com.pulumi.kubernetes.storage.v1.inputs.CSIDriverSpecArgs Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of kubernetes Show documentation
Show all versions of kubernetes Show documentation
A Pulumi package for creating and managing Kubernetes resources.
// *** WARNING: this file was generated by pulumi-java-gen. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***
package com.pulumi.kubernetes.storage.v1.inputs;
import com.pulumi.core.Output;
import com.pulumi.core.annotations.Import;
import com.pulumi.kubernetes.storage.v1.inputs.TokenRequestArgs;
import java.lang.Boolean;
import java.lang.String;
import java.util.List;
import java.util.Objects;
import java.util.Optional;
import javax.annotation.Nullable;
/**
* CSIDriverSpec is the specification of a CSIDriver.
*
*/
public final class CSIDriverSpecArgs extends com.pulumi.resources.ResourceArgs {
public static final CSIDriverSpecArgs Empty = new CSIDriverSpecArgs();
/**
* 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.
*
*/
@Import(name="attachRequired")
private @Nullable Output attachRequired;
/**
* @return 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.
*
*/
public Optional> attachRequired() {
return Optional.ofNullable(this.attachRequired);
}
/**
* fsGroupPolicy 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* 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.
*
*/
@Import(name="fsGroupPolicy")
private @Nullable Output fsGroupPolicy;
/**
* @return fsGroupPolicy 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* 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.
*
*/
public Optional> fsGroupPolicy() {
return Optional.ofNullable(this.fsGroupPolicy);
}
/**
* podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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 VolumeContext 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
*/
@Import(name="podInfoOnMount")
private @Nullable Output podInfoOnMount;
/**
* @return podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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 VolumeContext 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
*/
public Optional> podInfoOnMount() {
return Optional.ofNullable(this.podInfoOnMount);
}
/**
* 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.
*
*/
@Import(name="requiresRepublish")
private @Nullable Output requiresRepublish;
/**
* @return 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.
*
*/
public Optional> requiresRepublish() {
return Optional.ofNullable(this.requiresRepublish);
}
/**
* seLinuxMount specifies if the CSI driver supports "-o context" mount option.
*
* When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
*
* When "false", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.
*
* Default is "false".
*
*/
@Import(name="seLinuxMount")
private @Nullable Output seLinuxMount;
/**
* @return seLinuxMount specifies if the CSI driver supports "-o context" mount option.
*
* When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
*
* When "false", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.
*
* Default is "false".
*
*/
public Optional> seLinuxMount() {
return Optional.ofNullable(this.seLinuxMount);
}
/**
* 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, if set to true.
*
* 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.
*
*/
@Import(name="storageCapacity")
private @Nullable Output storageCapacity;
/**
* @return 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, if set to true.
*
* 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.
*
*/
public Optional> storageCapacity() {
return Optional.ofNullable(this.storageCapacity);
}
/**
* 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.
*
*/
@Import(name="tokenRequests")
private @Nullable Output> tokenRequests;
/**
* @return 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.
*
*/
public Optional>> tokenRequests() {
return Optional.ofNullable(this.tokenRequests);
}
/**
* 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.
*
*/
@Import(name="volumeLifecycleModes")
private @Nullable Output> volumeLifecycleModes;
/**
* @return 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.
*
*/
public Optional>> volumeLifecycleModes() {
return Optional.ofNullable(this.volumeLifecycleModes);
}
private CSIDriverSpecArgs() {}
private CSIDriverSpecArgs(CSIDriverSpecArgs $) {
this.attachRequired = $.attachRequired;
this.fsGroupPolicy = $.fsGroupPolicy;
this.podInfoOnMount = $.podInfoOnMount;
this.requiresRepublish = $.requiresRepublish;
this.seLinuxMount = $.seLinuxMount;
this.storageCapacity = $.storageCapacity;
this.tokenRequests = $.tokenRequests;
this.volumeLifecycleModes = $.volumeLifecycleModes;
}
public static Builder builder() {
return new Builder();
}
public static Builder builder(CSIDriverSpecArgs defaults) {
return new Builder(defaults);
}
public static final class Builder {
private CSIDriverSpecArgs $;
public Builder() {
$ = new CSIDriverSpecArgs();
}
public Builder(CSIDriverSpecArgs defaults) {
$ = new CSIDriverSpecArgs(Objects.requireNonNull(defaults));
}
/**
* @param attachRequired 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.
*
* @return builder
*
*/
public Builder attachRequired(@Nullable Output attachRequired) {
$.attachRequired = attachRequired;
return this;
}
/**
* @param attachRequired 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.
*
* @return builder
*
*/
public Builder attachRequired(Boolean attachRequired) {
return attachRequired(Output.of(attachRequired));
}
/**
* @param fsGroupPolicy fsGroupPolicy 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* 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.
*
* @return builder
*
*/
public Builder fsGroupPolicy(@Nullable Output fsGroupPolicy) {
$.fsGroupPolicy = fsGroupPolicy;
return this;
}
/**
* @param fsGroupPolicy fsGroupPolicy 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* 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.
*
* @return builder
*
*/
public Builder fsGroupPolicy(String fsGroupPolicy) {
return fsGroupPolicy(Output.of(fsGroupPolicy));
}
/**
* @param podInfoOnMount podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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 VolumeContext 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* @return builder
*
*/
public Builder podInfoOnMount(@Nullable Output podInfoOnMount) {
$.podInfoOnMount = podInfoOnMount;
return this;
}
/**
* @param podInfoOnMount podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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 VolumeContext 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 was immutable in Kubernetes < 1.29 and now is mutable.
*
* @return builder
*
*/
public Builder podInfoOnMount(Boolean podInfoOnMount) {
return podInfoOnMount(Output.of(podInfoOnMount));
}
/**
* @param requiresRepublish 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.
*
* @return builder
*
*/
public Builder requiresRepublish(@Nullable Output requiresRepublish) {
$.requiresRepublish = requiresRepublish;
return this;
}
/**
* @param requiresRepublish 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.
*
* @return builder
*
*/
public Builder requiresRepublish(Boolean requiresRepublish) {
return requiresRepublish(Output.of(requiresRepublish));
}
/**
* @param seLinuxMount seLinuxMount specifies if the CSI driver supports "-o context" mount option.
*
* When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
*
* When "false", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.
*
* Default is "false".
*
* @return builder
*
*/
public Builder seLinuxMount(@Nullable Output seLinuxMount) {
$.seLinuxMount = seLinuxMount;
return this;
}
/**
* @param seLinuxMount seLinuxMount specifies if the CSI driver supports "-o context" mount option.
*
* When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
*
* When "false", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.
*
* Default is "false".
*
* @return builder
*
*/
public Builder seLinuxMount(Boolean seLinuxMount) {
return seLinuxMount(Output.of(seLinuxMount));
}
/**
* @param storageCapacity 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, if set to true.
*
* 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.
*
* @return builder
*
*/
public Builder storageCapacity(@Nullable Output storageCapacity) {
$.storageCapacity = storageCapacity;
return this;
}
/**
* @param storageCapacity 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, if set to true.
*
* 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.
*
* @return builder
*
*/
public Builder storageCapacity(Boolean storageCapacity) {
return storageCapacity(Output.of(storageCapacity));
}
/**
* @param tokenRequests 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.
*
* @return builder
*
*/
public Builder tokenRequests(@Nullable Output> tokenRequests) {
$.tokenRequests = tokenRequests;
return this;
}
/**
* @param tokenRequests 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.
*
* @return builder
*
*/
public Builder tokenRequests(List tokenRequests) {
return tokenRequests(Output.of(tokenRequests));
}
/**
* @param tokenRequests 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.
*
* @return builder
*
*/
public Builder tokenRequests(TokenRequestArgs... tokenRequests) {
return tokenRequests(List.of(tokenRequests));
}
/**
* @param volumeLifecycleModes 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.
*
* @return builder
*
*/
public Builder volumeLifecycleModes(@Nullable Output> volumeLifecycleModes) {
$.volumeLifecycleModes = volumeLifecycleModes;
return this;
}
/**
* @param volumeLifecycleModes 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.
*
* @return builder
*
*/
public Builder volumeLifecycleModes(List volumeLifecycleModes) {
return volumeLifecycleModes(Output.of(volumeLifecycleModes));
}
/**
* @param volumeLifecycleModes 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.
*
* @return builder
*
*/
public Builder volumeLifecycleModes(String... volumeLifecycleModes) {
return volumeLifecycleModes(List.of(volumeLifecycleModes));
}
public CSIDriverSpecArgs build() {
return $;
}
}
}
© 2015 - 2024 Weber Informatics LLC | Privacy Policy