Package io.kubernetes.client.proto

Class V1Storage.CSIDriverSpec.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderType>
com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>
io.kubernetes.client.proto.V1Storage.CSIDriverSpec.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, V1Storage.CSIDriverSpecOrBuilder, Cloneable
Enclosing class:
V1Storage.CSIDriverSpec
public static final class V1Storage.CSIDriverSpec.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder> implements V1Storage.CSIDriverSpecOrBuilder
 CSIDriverSpec is the specification of a CSIDriver.
Protobuf type k8s.io.api.storage.v1.CSIDriverSpec

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • clear

      public V1Storage.CSIDriverSpec.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • getDefaultInstanceForType

      public V1Storage.CSIDriverSpec getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public V1Storage.CSIDriverSpec build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public V1Storage.CSIDriverSpec buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public V1Storage.CSIDriverSpec.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • setField

      public V1Storage.CSIDriverSpec.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • clearField

      public V1Storage.CSIDriverSpec.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • clearOneof

      public V1Storage.CSIDriverSpec.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • setRepeatedField

      public V1Storage.CSIDriverSpec.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • addRepeatedField

      public V1Storage.CSIDriverSpec.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • mergeFrom

      public V1Storage.CSIDriverSpec.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1Storage.CSIDriverSpec.Builder>

    • mergeFrom

      public V1Storage.CSIDriverSpec.Builder mergeFrom(V1Storage.CSIDriverSpec other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • mergeFrom

      public V1Storage.CSIDriverSpec.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1Storage.CSIDriverSpec.Builder>
      Throws:
      IOException

    • hasAttachRequired

      public boolean hasAttachRequired()
       attachRequired indicates this CSI volume driver requires an attach
 operation (because it implements the CSI ControllerPublishVolume()
 method), and that the Kubernetes attach detach controller should call
 the attach volume interface which checks the volumeattachment status
 and waits until the volume is attached before proceeding to mounting.
 The CSI external-attacher coordinates with CSI volume driver and updates
 the volumeattachment status when the attach operation is complete.
 If the CSIDriverRegistry feature gate is enabled and the value is
 specified to false, the attach operation will be skipped.
 Otherwise the attach operation will be called.
 This field is immutable.
 +optional
      optional bool attachRequired = 1;
      Specified by:
      hasAttachRequired in interface V1Storage.CSIDriverSpecOrBuilder

    • getAttachRequired

      public boolean getAttachRequired()
       attachRequired indicates this CSI volume driver requires an attach
 operation (because it implements the CSI ControllerPublishVolume()
 method), and that the Kubernetes attach detach controller should call
 the attach volume interface which checks the volumeattachment status
 and waits until the volume is attached before proceeding to mounting.
 The CSI external-attacher coordinates with CSI volume driver and updates
 the volumeattachment status when the attach operation is complete.
 If the CSIDriverRegistry feature gate is enabled and the value is
 specified to false, the attach operation will be skipped.
 Otherwise the attach operation will be called.
 This field is immutable.
 +optional
      optional bool attachRequired = 1;
      Specified by:
      getAttachRequired in interface V1Storage.CSIDriverSpecOrBuilder

    • setAttachRequired

      public V1Storage.CSIDriverSpec.Builder setAttachRequired(boolean value)
       attachRequired indicates this CSI volume driver requires an attach
 operation (because it implements the CSI ControllerPublishVolume()
 method), and that the Kubernetes attach detach controller should call
 the attach volume interface which checks the volumeattachment status
 and waits until the volume is attached before proceeding to mounting.
 The CSI external-attacher coordinates with CSI volume driver and updates
 the volumeattachment status when the attach operation is complete.
 If the CSIDriverRegistry feature gate is enabled and the value is
 specified to false, the attach operation will be skipped.
 Otherwise the attach operation will be called.
 This field is immutable.
 +optional
      optional bool attachRequired = 1;

    • clearAttachRequired

      public V1Storage.CSIDriverSpec.Builder clearAttachRequired()
       attachRequired indicates this CSI volume driver requires an attach
 operation (because it implements the CSI ControllerPublishVolume()
 method), and that the Kubernetes attach detach controller should call
 the attach volume interface which checks the volumeattachment status
 and waits until the volume is attached before proceeding to mounting.
 The CSI external-attacher coordinates with CSI volume driver and updates
 the volumeattachment status when the attach operation is complete.
 If the CSIDriverRegistry feature gate is enabled and the value is
 specified to false, the attach operation will be skipped.
 Otherwise the attach operation will be called.
 This field is immutable.
 +optional
      optional bool attachRequired = 1;

    • hasPodInfoOnMount

      public boolean hasPodInfoOnMount()
       If set to true, podInfoOnMount indicates this CSI volume driver
 requires additional pod information (like podName, podUID, etc.) during
 mount operations.
 If set to false, pod information will not be passed on mount.
 Default is false.
 The CSI driver specifies podInfoOnMount as part of driver deployment.
 If true, Kubelet will pass pod information as VolumeContext in the CSI
 NodePublishVolume() calls.
 The CSI driver is responsible for parsing and validating the information
 passed in as VolumeContext.
 The following VolumeConext will be passed if podInfoOnMount is set to true.
 This list might grow, but the prefix will be used.
 "csi.storage.k8s.io/pod.name": pod.Name
 "csi.storage.k8s.io/pod.namespace": pod.Namespace
 "csi.storage.k8s.io/pod.uid": string(pod.UID)
 "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
                                 defined by a CSIVolumeSource, otherwise "false"
 "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only
 required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode.
 Other drivers can leave pod info disabled and/or ignore this field.
 As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when
 deployed on such a cluster and the deployment determines which mode that is, for example
 via a command line parameter of the driver.
 This field is immutable.
 +optional
      optional bool podInfoOnMount = 2;
      Specified by:
      hasPodInfoOnMount in interface V1Storage.CSIDriverSpecOrBuilder

    • getPodInfoOnMount

      public boolean getPodInfoOnMount()
       If set to true, podInfoOnMount indicates this CSI volume driver
 requires additional pod information (like podName, podUID, etc.) during
 mount operations.
 If set to false, pod information will not be passed on mount.
 Default is false.
 The CSI driver specifies podInfoOnMount as part of driver deployment.
 If true, Kubelet will pass pod information as VolumeContext in the CSI
 NodePublishVolume() calls.
 The CSI driver is responsible for parsing and validating the information
 passed in as VolumeContext.
 The following VolumeConext will be passed if podInfoOnMount is set to true.
 This list might grow, but the prefix will be used.
 "csi.storage.k8s.io/pod.name": pod.Name
 "csi.storage.k8s.io/pod.namespace": pod.Namespace
 "csi.storage.k8s.io/pod.uid": string(pod.UID)
 "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
                                 defined by a CSIVolumeSource, otherwise "false"
 "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only
 required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode.
 Other drivers can leave pod info disabled and/or ignore this field.
 As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when
 deployed on such a cluster and the deployment determines which mode that is, for example
 via a command line parameter of the driver.
 This field is immutable.
 +optional
      optional bool podInfoOnMount = 2;
      Specified by:
      getPodInfoOnMount in interface V1Storage.CSIDriverSpecOrBuilder

    • setPodInfoOnMount

      public V1Storage.CSIDriverSpec.Builder setPodInfoOnMount(boolean value)
       If set to true, podInfoOnMount indicates this CSI volume driver
 requires additional pod information (like podName, podUID, etc.) during
 mount operations.
 If set to false, pod information will not be passed on mount.
 Default is false.
 The CSI driver specifies podInfoOnMount as part of driver deployment.
 If true, Kubelet will pass pod information as VolumeContext in the CSI
 NodePublishVolume() calls.
 The CSI driver is responsible for parsing and validating the information
 passed in as VolumeContext.
 The following VolumeConext will be passed if podInfoOnMount is set to true.
 This list might grow, but the prefix will be used.
 "csi.storage.k8s.io/pod.name": pod.Name
 "csi.storage.k8s.io/pod.namespace": pod.Namespace
 "csi.storage.k8s.io/pod.uid": string(pod.UID)
 "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
                                 defined by a CSIVolumeSource, otherwise "false"
 "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only
 required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode.
 Other drivers can leave pod info disabled and/or ignore this field.
 As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when
 deployed on such a cluster and the deployment determines which mode that is, for example
 via a command line parameter of the driver.
 This field is immutable.
 +optional
      optional bool podInfoOnMount = 2;

    • clearPodInfoOnMount

      public V1Storage.CSIDriverSpec.Builder clearPodInfoOnMount()
       If set to true, podInfoOnMount indicates this CSI volume driver
 requires additional pod information (like podName, podUID, etc.) during
 mount operations.
 If set to false, pod information will not be passed on mount.
 Default is false.
 The CSI driver specifies podInfoOnMount as part of driver deployment.
 If true, Kubelet will pass pod information as VolumeContext in the CSI
 NodePublishVolume() calls.
 The CSI driver is responsible for parsing and validating the information
 passed in as VolumeContext.
 The following VolumeConext will be passed if podInfoOnMount is set to true.
 This list might grow, but the prefix will be used.
 "csi.storage.k8s.io/pod.name": pod.Name
 "csi.storage.k8s.io/pod.namespace": pod.Namespace
 "csi.storage.k8s.io/pod.uid": string(pod.UID)
 "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
                                 defined by a CSIVolumeSource, otherwise "false"
 "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only
 required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode.
 Other drivers can leave pod info disabled and/or ignore this field.
 As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when
 deployed on such a cluster and the deployment determines which mode that is, for example
 via a command line parameter of the driver.
 This field is immutable.
 +optional
      optional bool podInfoOnMount = 2;

    • getVolumeLifecycleModesList

      public com.google.protobuf.ProtocolStringList getVolumeLifecycleModesList()
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;
      Specified by:
      getVolumeLifecycleModesList in interface V1Storage.CSIDriverSpecOrBuilder

    • getVolumeLifecycleModesCount

      public int getVolumeLifecycleModesCount()
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;
      Specified by:
      getVolumeLifecycleModesCount in interface V1Storage.CSIDriverSpecOrBuilder

    • getVolumeLifecycleModes

      public String getVolumeLifecycleModes(int index)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;
      Specified by:
      getVolumeLifecycleModes in interface V1Storage.CSIDriverSpecOrBuilder

    • getVolumeLifecycleModesBytes

      public com.google.protobuf.ByteString getVolumeLifecycleModesBytes(int index)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;
      Specified by:
      getVolumeLifecycleModesBytes in interface V1Storage.CSIDriverSpecOrBuilder

    • setVolumeLifecycleModes

      public V1Storage.CSIDriverSpec.Builder setVolumeLifecycleModes(int index, String value)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;

    • addVolumeLifecycleModes

      public V1Storage.CSIDriverSpec.Builder addVolumeLifecycleModes(String value)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;

    • addAllVolumeLifecycleModes

      public V1Storage.CSIDriverSpec.Builder addAllVolumeLifecycleModes(Iterable<String> values)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;

    • clearVolumeLifecycleModes

      public V1Storage.CSIDriverSpec.Builder clearVolumeLifecycleModes()
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;

    • addVolumeLifecycleModesBytes

      public V1Storage.CSIDriverSpec.Builder addVolumeLifecycleModesBytes(com.google.protobuf.ByteString value)
       volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
 The default if the list is empty is "Persistent", which is the usage
 defined by the CSI specification and implemented in Kubernetes via the usual
 PV/PVC mechanism.
 The other mode is "Ephemeral". In this mode, volumes are defined inline
 inside the pod spec with CSIVolumeSource and their lifecycle is tied to
 the lifecycle of that pod. A driver has to be aware of this
 because it is only going to get a NodePublishVolume call for such a volume.
 For more information about implementing this mode, see
 https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
 A driver can support one or more of these modes and
 more modes may be added in the future.
 This field is beta.
 This field is immutable.
 +optional
 +listType=set
      repeated string volumeLifecycleModes = 3;

    • hasStorageCapacity

      public boolean hasStorageCapacity()
       If set to true, storageCapacity indicates that the CSI
 volume driver wants pod scheduling to consider the storage
 capacity that the driver deployment will report by creating
 CSIStorageCapacity objects with capacity information.
 The check can be enabled immediately when deploying a driver.
 In that case, provisioning new volumes with late binding
 will pause until the driver deployment has published
 some suitable CSIStorageCapacity object.
 Alternatively, the driver can be deployed with the field
 unset or false and it can be flipped later when storage
 capacity information has been published.
 This field was immutable in Kubernetes <= 1.22 and now is mutable.
 This is a beta field and only available when the CSIStorageCapacity
 feature is enabled. The default is false.
 +optional
 +featureGate=CSIStorageCapacity
      optional bool storageCapacity = 4;
      Specified by:
      hasStorageCapacity in interface V1Storage.CSIDriverSpecOrBuilder

    • getStorageCapacity

      public boolean getStorageCapacity()
       If set to true, storageCapacity indicates that the CSI
 volume driver wants pod scheduling to consider the storage
 capacity that the driver deployment will report by creating
 CSIStorageCapacity objects with capacity information.
 The check can be enabled immediately when deploying a driver.
 In that case, provisioning new volumes with late binding
 will pause until the driver deployment has published
 some suitable CSIStorageCapacity object.
 Alternatively, the driver can be deployed with the field
 unset or false and it can be flipped later when storage
 capacity information has been published.
 This field was immutable in Kubernetes <= 1.22 and now is mutable.
 This is a beta field and only available when the CSIStorageCapacity
 feature is enabled. The default is false.
 +optional
 +featureGate=CSIStorageCapacity
      optional bool storageCapacity = 4;
      Specified by:
      getStorageCapacity in interface V1Storage.CSIDriverSpecOrBuilder

    • setStorageCapacity

      public V1Storage.CSIDriverSpec.Builder setStorageCapacity(boolean value)
       If set to true, storageCapacity indicates that the CSI
 volume driver wants pod scheduling to consider the storage
 capacity that the driver deployment will report by creating
 CSIStorageCapacity objects with capacity information.
 The check can be enabled immediately when deploying a driver.
 In that case, provisioning new volumes with late binding
 will pause until the driver deployment has published
 some suitable CSIStorageCapacity object.
 Alternatively, the driver can be deployed with the field
 unset or false and it can be flipped later when storage
 capacity information has been published.
 This field was immutable in Kubernetes <= 1.22 and now is mutable.
 This is a beta field and only available when the CSIStorageCapacity
 feature is enabled. The default is false.
 +optional
 +featureGate=CSIStorageCapacity
      optional bool storageCapacity = 4;

    • clearStorageCapacity

      public V1Storage.CSIDriverSpec.Builder clearStorageCapacity()
       If set to true, storageCapacity indicates that the CSI
 volume driver wants pod scheduling to consider the storage
 capacity that the driver deployment will report by creating
 CSIStorageCapacity objects with capacity information.
 The check can be enabled immediately when deploying a driver.
 In that case, provisioning new volumes with late binding
 will pause until the driver deployment has published
 some suitable CSIStorageCapacity object.
 Alternatively, the driver can be deployed with the field
 unset or false and it can be flipped later when storage
 capacity information has been published.
 This field was immutable in Kubernetes <= 1.22 and now is mutable.
 This is a beta field and only available when the CSIStorageCapacity
 feature is enabled. The default is false.
 +optional
 +featureGate=CSIStorageCapacity
      optional bool storageCapacity = 4;

    • hasFsGroupPolicy

      public boolean hasFsGroupPolicy()
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;
      Specified by:
      hasFsGroupPolicy in interface V1Storage.CSIDriverSpecOrBuilder

    • getFsGroupPolicy

      public String getFsGroupPolicy()
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;
      Specified by:
      getFsGroupPolicy in interface V1Storage.CSIDriverSpecOrBuilder

    • getFsGroupPolicyBytes

      public com.google.protobuf.ByteString getFsGroupPolicyBytes()
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;
      Specified by:
      getFsGroupPolicyBytes in interface V1Storage.CSIDriverSpecOrBuilder

    • setFsGroupPolicy

      public V1Storage.CSIDriverSpec.Builder setFsGroupPolicy(String value)
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;

    • clearFsGroupPolicy

      public V1Storage.CSIDriverSpec.Builder clearFsGroupPolicy()
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;

    • setFsGroupPolicyBytes

      public V1Storage.CSIDriverSpec.Builder setFsGroupPolicyBytes(com.google.protobuf.ByteString value)
       Defines if the underlying volume supports changing ownership and
 permission of the volume before being mounted.
 Refer to the specific FSGroupPolicy values for additional details.
 This field is immutable.
 Defaults to ReadWriteOnceWithFSType, which will examine each volume
 to determine if Kubernetes should modify ownership and permissions of the volume.
 With the default policy the defined fsGroup will only be applied
 if a fstype is defined and the volume's access mode contains ReadWriteOnce.
 +optional
      optional string fsGroupPolicy = 5;

    • getTokenRequestsList

      public List<V1Storage.TokenRequest> getTokenRequestsList()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;
      Specified by:
      getTokenRequestsList in interface V1Storage.CSIDriverSpecOrBuilder

    • getTokenRequestsCount

      public int getTokenRequestsCount()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;
      Specified by:
      getTokenRequestsCount in interface V1Storage.CSIDriverSpecOrBuilder

    • getTokenRequests

      public V1Storage.TokenRequest getTokenRequests(int index)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;
      Specified by:
      getTokenRequests in interface V1Storage.CSIDriverSpecOrBuilder

    • setTokenRequests

      public V1Storage.CSIDriverSpec.Builder setTokenRequests(int index, V1Storage.TokenRequest value)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • setTokenRequests

      public V1Storage.CSIDriverSpec.Builder setTokenRequests(int index, V1Storage.TokenRequest.Builder builderForValue)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addTokenRequests

      public V1Storage.CSIDriverSpec.Builder addTokenRequests(V1Storage.TokenRequest value)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addTokenRequests

      public V1Storage.CSIDriverSpec.Builder addTokenRequests(int index, V1Storage.TokenRequest value)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addTokenRequests

      public V1Storage.CSIDriverSpec.Builder addTokenRequests(V1Storage.TokenRequest.Builder builderForValue)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addTokenRequests

      public V1Storage.CSIDriverSpec.Builder addTokenRequests(int index, V1Storage.TokenRequest.Builder builderForValue)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addAllTokenRequests

      public V1Storage.CSIDriverSpec.Builder addAllTokenRequests(Iterable<? extends V1Storage.TokenRequest> values)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • clearTokenRequests

      public V1Storage.CSIDriverSpec.Builder clearTokenRequests()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • removeTokenRequests

      public V1Storage.CSIDriverSpec.Builder removeTokenRequests(int index)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • getTokenRequestsBuilder

      public V1Storage.TokenRequest.Builder getTokenRequestsBuilder(int index)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • getTokenRequestsOrBuilder

      public V1Storage.TokenRequestOrBuilder getTokenRequestsOrBuilder(int index)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;
      Specified by:
      getTokenRequestsOrBuilder in interface V1Storage.CSIDriverSpecOrBuilder

    • getTokenRequestsOrBuilderList

      public List<? extends V1Storage.TokenRequestOrBuilder> getTokenRequestsOrBuilderList()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;
      Specified by:
      getTokenRequestsOrBuilderList in interface V1Storage.CSIDriverSpecOrBuilder

    • addTokenRequestsBuilder

      public V1Storage.TokenRequest.Builder addTokenRequestsBuilder()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • addTokenRequestsBuilder

      public V1Storage.TokenRequest.Builder addTokenRequestsBuilder(int index)
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • getTokenRequestsBuilderList

      public List<V1Storage.TokenRequest.Builder> getTokenRequestsBuilderList()
       TokenRequests indicates the CSI driver needs pods' service account
 tokens it is mounting volume for to do necessary authentication. Kubelet
 will pass the tokens in VolumeContext in the CSI NodePublishVolume calls.
 The CSI driver should parse and validate the following VolumeContext:
 "csi.storage.k8s.io/serviceAccount.tokens": {
   "<audience>": {
     "token": <token>,
     "expirationTimestamp": <expiration timestamp in RFC3339>,
   },
   ...
 }
 Note: Audience in each TokenRequest should be different and at
 most one token is empty string. To receive a new token after expiry,
 RequiresRepublish can be used to trigger NodePublishVolume periodically.
 +optional
 +listType=atomic
      repeated .k8s.io.api.storage.v1.TokenRequest tokenRequests = 6;

    • hasRequiresRepublish

      public boolean hasRequiresRepublish()
       RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
 being periodically called to reflect any possible change in the mounted
 volume. This field defaults to false.
 Note: After a successful initial NodePublishVolume call, subsequent calls
 to NodePublishVolume should only update the contents of the volume. New
 mount points will not be seen by a running container.
 +optional
      optional bool requiresRepublish = 7;
      Specified by:
      hasRequiresRepublish in interface V1Storage.CSIDriverSpecOrBuilder

    • getRequiresRepublish

      public boolean getRequiresRepublish()
       RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
 being periodically called to reflect any possible change in the mounted
 volume. This field defaults to false.
 Note: After a successful initial NodePublishVolume call, subsequent calls
 to NodePublishVolume should only update the contents of the volume. New
 mount points will not be seen by a running container.
 +optional
      optional bool requiresRepublish = 7;
      Specified by:
      getRequiresRepublish in interface V1Storage.CSIDriverSpecOrBuilder

    • setRequiresRepublish

      public V1Storage.CSIDriverSpec.Builder setRequiresRepublish(boolean value)
       RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
 being periodically called to reflect any possible change in the mounted
 volume. This field defaults to false.
 Note: After a successful initial NodePublishVolume call, subsequent calls
 to NodePublishVolume should only update the contents of the volume. New
 mount points will not be seen by a running container.
 +optional
      optional bool requiresRepublish = 7;

    • clearRequiresRepublish

      public V1Storage.CSIDriverSpec.Builder clearRequiresRepublish()
       RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
 being periodically called to reflect any possible change in the mounted
 volume. This field defaults to false.
 Note: After a successful initial NodePublishVolume call, subsequent calls
 to NodePublishVolume should only update the contents of the volume. New
 mount points will not be seen by a running container.
 +optional
      optional bool requiresRepublish = 7;

    • setUnknownFields

      public final V1Storage.CSIDriverSpec.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>

    • mergeUnknownFields

      public final V1Storage.CSIDriverSpec.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1Storage.CSIDriverSpec.Builder>