![]() As noted above, a CSI driver is not suitable for CSI ephemeral inline volumes when volume creation requires volumeAttributes that should be restricted to an administrator. Security ConsiderationsĬSI driver vendors that choose to support ephemeral inline volumes are responsible for secure handling of these volumes, and special consideration needs to be given to what volumeAttributes are supported by the driver. Such a driver can also support CSIĮphemeral inline volumes if desired. Supports dynamic provisioning of volumes. StorageClassName: "scratch-storage-class"Ī CSI driver is suitable for generic ephemeral inline volumes if it Generic ephemeral inline volumes make the normal volume API (storageĬlasses, PersistentVolumeClaim) usable for ephemeral inline Ephemeral inline volumes allow these attributes to be setĭirectly in the Pod spec, and so are not restricted to an admin. To an administrator, for example parameters that are otherwise set in a ephemeral volume creation requires volumeAttributes that should be restricted.Which do not support generic ephemeral volumesĪ CSI driver is not suitable for CSI ephemeral inline volumes when: ephemeral inline volumes have to be supported on Kubernetes clusters.none of the usual volume features (restoring from snapshot,.Turns out to be insufficient is not needed rescheduling of pods onto a different node when storage capacity.resource usage on the node is small and/or does not need to be exposed.it can create volumes when running on a node.Like drivers that provide secrets to a pod it serves a special purpose and needs custom per-volume parameters,.apiVersion: v1Ī CSI driver is suitable for CSI ephemeral inline volumes if: Storage classes are not supported andĪll parameters are driver specific. Parameters that determine the content of the volume can be specified Which feature should my driver support?ĬSI ephemeral inline volumes are meant for simple, local volumes. The user facingĭocumentation for both features is in the Kubernetesĭocumentation. Have different APIs and different implementations.Įnhancement proposals for design details. However, the two features are targeted at different use cases and thus Kubernetes and the driver handle all phases of volume operations as Volumes follow the ephemeral lifecycle of their associated pods where In both features, the volumes are specified directly in the pod ![]() The Pod's lifecycle: CSI ephemeral volumes and generic ephemeral Two different Kubernetes features allow volumes to follow With a PersistentVolume and PersistentVolumeClaim objectĬombination. Traditionally, volumes that are backed by CSI drivers can only be used Pod Inline Volume Support Status CSI Ephemeral Inline Volumes Status Versioning, Support, Compatibility Policies
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |