#VCP #Storage #Concept With the introduction of Tanzu, VMware also introduces another Storage concept called Cloud Native Storage or CNS. Through the CNS you implement the provisioning and lifecycle operations for persistent volumes. ## Ephemeral virtual disks temporary storage for objects like logs or temporary data of the Pod. Once the pod does no longer exist the disk is removed aswell. Disk persists across restarts. ## Container Image virtual disks contains the software that is to be run. When the pod is deleted the virtual disks are detached. ## Persistent volume virtual disks Persistent storage that is attached to Pods for data and other objects. Are backed by First Class Disks(Virtual disks). Is identified by UUIDs which are valid even when disk is moved or snapshotted. ### With dynamic Provisioning Storage does not need to be pre-provisioned. Persistent volumes can be created on-demand. ### With static provisioning use an existing storage object and make it available to the cluster. Manually created virtual disk as backing storage for the persistent volume. Only Tanzu Kubernetes Clusters support static provisioning. ## vSphere CNS-CSI [[../../../Concepts/Kubernetes - CSI (Container Storage Interface|Kubernetes - CSI (Container Storage Interface|[Container Storage Interface)]]]].md) Provides an interface to orchestrators like Kubernetes on a Supervisor Namespace. Is in communication directly with the CNS. Handles storage requests that come from vSPhere Pods and Tanzu Kubernetes Cluster. Aditionally vSpheres CSI plugin allows for Snapshots, cloning data protection. ## Paravirtual CSI(pvCSI) Driver that has been modified for Tanzu Kubernetes. Manages all the storage requests from the Tanzu clusters and forwards it to the CSI vsphere Plugin. vSphere Pods are not using the pvCSI controller. ![[_media/vSphere - Storage-2024-05-14.png]] ## 🔗Resources