public static final class V1beta1Storage.CSIDriverSpec.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder> implements V1beta1Storage.CSIDriverSpecOrBuilder
CSIDriverSpec is the specification of a CSIDriver.Protobuf type
k8s.io.api.storage.v1beta1.CSIDriverSpec| Modifier and Type | Method and Description |
|---|---|
V1beta1Storage.CSIDriverSpec.Builder |
addAllTokenRequests(Iterable<? extends V1beta1Storage.TokenRequest> values)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
addAllVolumeLifecycleModes(Iterable<String> values)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
V1beta1Storage.CSIDriverSpec.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
V1beta1Storage.CSIDriverSpec.Builder |
addTokenRequests(int index,
V1beta1Storage.TokenRequest.Builder builderForValue)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
addTokenRequests(int index,
V1beta1Storage.TokenRequest value)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
addTokenRequests(V1beta1Storage.TokenRequest.Builder builderForValue)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
addTokenRequests(V1beta1Storage.TokenRequest value)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.TokenRequest.Builder |
addTokenRequestsBuilder()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.TokenRequest.Builder |
addTokenRequestsBuilder(int index)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
addVolumeLifecycleModes(String value)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
V1beta1Storage.CSIDriverSpec.Builder |
addVolumeLifecycleModesBytes(com.google.protobuf.ByteString value)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
V1beta1Storage.CSIDriverSpec |
build() |
V1beta1Storage.CSIDriverSpec |
buildPartial() |
V1beta1Storage.CSIDriverSpec.Builder |
clear() |
V1beta1Storage.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.
|
V1beta1Storage.CSIDriverSpec.Builder |
clearField(com.google.protobuf.Descriptors.FieldDescriptor field) |
V1beta1Storage.CSIDriverSpec.Builder |
clearFsGroupPolicy()
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
V1beta1Storage.CSIDriverSpec.Builder |
clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) |
V1beta1Storage.CSIDriverSpec.Builder |
clearPodInfoOnMount()
If set to true, podInfoOnMount indicates this CSI volume driver
requires additional pod information (like podName, podUID, etc.) during
mount operations.
|
V1beta1Storage.CSIDriverSpec.Builder |
clearRequiresRepublish()
RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
being periodically called to reflect any possible change in the mounted
volume.
|
V1beta1Storage.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.
|
V1beta1Storage.CSIDriverSpec.Builder |
clearTokenRequests()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
clearVolumeLifecycleModes()
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
V1beta1Storage.CSIDriverSpec.Builder |
clone() |
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.
|
V1beta1Storage.CSIDriverSpec |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
String |
getFsGroupPolicy()
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
com.google.protobuf.ByteString |
getFsGroupPolicyBytes()
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
boolean |
getPodInfoOnMount()
If set to true, podInfoOnMount indicates this CSI volume driver
requires additional pod information (like podName, podUID, etc.) during
mount operations.
|
boolean |
getRequiresRepublish()
RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
being periodically called to reflect any possible change in the mounted
volume.
|
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.
|
V1beta1Storage.TokenRequest |
getTokenRequests(int index)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.TokenRequest.Builder |
getTokenRequestsBuilder(int index)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
List<V1beta1Storage.TokenRequest.Builder> |
getTokenRequestsBuilderList()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
int |
getTokenRequestsCount()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
List<V1beta1Storage.TokenRequest> |
getTokenRequestsList()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.TokenRequestOrBuilder |
getTokenRequestsOrBuilder(int index)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
List<? extends V1beta1Storage.TokenRequestOrBuilder> |
getTokenRequestsOrBuilderList()
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
String |
getVolumeLifecycleModes(int index)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
com.google.protobuf.ByteString |
getVolumeLifecycleModesBytes(int index)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
int |
getVolumeLifecycleModesCount()
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
com.google.protobuf.ProtocolStringList |
getVolumeLifecycleModesList()
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
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.
|
boolean |
hasFsGroupPolicy()
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
boolean |
hasPodInfoOnMount()
If set to true, podInfoOnMount indicates this CSI volume driver
requires additional pod information (like podName, podUID, etc.) during
mount operations.
|
boolean |
hasRequiresRepublish()
RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
being periodically called to reflect any possible change in the mounted
volume.
|
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.
|
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
V1beta1Storage.CSIDriverSpec.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
V1beta1Storage.CSIDriverSpec.Builder |
mergeFrom(com.google.protobuf.Message other) |
V1beta1Storage.CSIDriverSpec.Builder |
mergeFrom(V1beta1Storage.CSIDriverSpec other) |
V1beta1Storage.CSIDriverSpec.Builder |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
V1beta1Storage.CSIDriverSpec.Builder |
removeTokenRequests(int index)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.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.
|
V1beta1Storage.CSIDriverSpec.Builder |
setField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
V1beta1Storage.CSIDriverSpec.Builder |
setFsGroupPolicy(String value)
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
V1beta1Storage.CSIDriverSpec.Builder |
setFsGroupPolicyBytes(com.google.protobuf.ByteString value)
Defines if the underlying volume supports changing ownership and
permission of the volume before being mounted.
|
V1beta1Storage.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.
|
V1beta1Storage.CSIDriverSpec.Builder |
setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
int index,
Object value) |
V1beta1Storage.CSIDriverSpec.Builder |
setRequiresRepublish(boolean value)
RequiresRepublish indicates the CSI driver wants `NodePublishVolume`
being periodically called to reflect any possible change in the mounted
volume.
|
V1beta1Storage.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.
|
V1beta1Storage.CSIDriverSpec.Builder |
setTokenRequests(int index,
V1beta1Storage.TokenRequest.Builder builderForValue)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
setTokenRequests(int index,
V1beta1Storage.TokenRequest value)
TokenRequests indicates the CSI driver needs pods' service account
tokens it is mounting volume for to do necessary authentication.
|
V1beta1Storage.CSIDriverSpec.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
V1beta1Storage.CSIDriverSpec.Builder |
setVolumeLifecycleModes(int index,
String value)
VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
|
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitfindInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic V1beta1Storage.CSIDriverSpec build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic V1beta1Storage.CSIDriverSpec buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic V1beta1Storage.CSIDriverSpec.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder mergeFrom(V1beta1Storage.CSIDriverSpec other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public V1beta1Storage.CSIDriverSpec.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1beta1Storage.CSIDriverSpec.Builder>IOExceptionpublic 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;hasAttachRequired in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getAttachRequired in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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;public V1beta1Storage.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;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;hasPodInfoOnMount in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getPodInfoOnMount in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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;public V1beta1Storage.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;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 immutable. +optional
repeated string volumeLifecycleModes = 3;getVolumeLifecycleModesList in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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 immutable. +optional
repeated string volumeLifecycleModes = 3;getVolumeLifecycleModesCount in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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 immutable. +optional
repeated string volumeLifecycleModes = 3;getVolumeLifecycleModes in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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 immutable. +optional
repeated string volumeLifecycleModes = 3;getVolumeLifecycleModesBytes in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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 immutable. +optional
repeated string volumeLifecycleModes = 3;public V1beta1Storage.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 immutable. +optional
repeated string volumeLifecycleModes = 3;public V1beta1Storage.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 immutable. +optional
repeated string volumeLifecycleModes = 3;public V1beta1Storage.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 immutable. +optional
repeated string volumeLifecycleModes = 3;public V1beta1Storage.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 immutable. +optional
repeated string volumeLifecycleModes = 3;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;hasStorageCapacity in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getStorageCapacity in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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;public V1beta1Storage.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;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;hasFsGroupPolicy in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getFsGroupPolicy in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getFsGroupPolicyBytes in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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;public V1beta1Storage.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;public V1beta1Storage.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;public List<V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;getTokenRequestsList in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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.v1beta1.TokenRequest tokenRequests = 6;getTokenRequestsCount in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;getTokenRequests in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.CSIDriverSpec.Builder setTokenRequests(int index, V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder setTokenRequests(int index, V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder addTokenRequests(V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder addTokenRequests(int index, V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder addTokenRequests(V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder addTokenRequests(int index, V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.CSIDriverSpec.Builder addAllTokenRequests(Iterable<? extends V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;getTokenRequestsOrBuilder in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic List<? extends V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;getTokenRequestsOrBuilderList in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;public List<V1beta1Storage.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.v1beta1.TokenRequest tokenRequests = 6;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;hasRequiresRepublish in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic 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;getRequiresRepublish in interface V1beta1Storage.CSIDriverSpecOrBuilderpublic V1beta1Storage.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;public V1beta1Storage.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;public final V1beta1Storage.CSIDriverSpec.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>public final V1beta1Storage.CSIDriverSpec.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1beta1Storage.CSIDriverSpec.Builder>Copyright © 2023. All rights reserved.