vSphere Container Storage Plug-in for Kubernetes supports a number of different Kubernetes features that include block volumes, file volumes, volume expansion, and so on.
What to read next
Provisioning Block Volumes with vSphere Container Storage Plug-in vSphere Container Storage Plug-in supports dynamic provisioning and static provisioning of block volumes in a native, also called vanilla, Kubernetes cluster that you deploy in vSphere environment.Using Raw Block Volumes with vSphere Container Storage Plug-in vSphere Container Storage Plug-in supports block based volumes, also called raw block volumes. You can use this functionality to expose a persistent volume inside a container as a block device rather than a mounted file system.Provisioning File Volumes with vSphere Container Storage Plug-in vSphere Container Storage Plug-in V2.0 and above for native Kubernetes clusters supports file volumes backed by vSAN file shares. File volumes can be created statically or dynamically and mounted by stateful containerized applications. When using file volumes with the vSphere Container Storage Plug-in , you can reference the same shared data among multiple pods spread across different clusters. This is a mandatory requirement for applications that need shareability.Topology-Aware Volume Provisioning racks , regions , or zones , or use some other type of grouping. When topology is enabled in the cluster, you can use vSphere Container Storage Plug-in to deploy a Kubernetes workload to a specific region or zone defined in the topology.Provisioning Volumes in an Environment with Multiple vCenter Server Instances vSphere Container Storage Plug-in supports volume provisioning in an environment with multiple vCenter Server instances. As a result, you can provision volumes in a native Kubernetes cluster that spans across multiple vCenter Server instances.Expanding a Volume with vSphere Container Storage Plug-in vSphere Container Storage Plug-in supports volume expansion for block volumes that are created dynamically or statically. Deploy Kubernetes and Persistent Volumes on a vSAN Stretched Cluster vSAN stretched clusters. You can deploy multiple Kubernetes clusters with different storage requirements in the same vSAN stretched cluster.Using vSphere Container Storage Plug-in for HCI Mesh Deployment vSphere Container Storage Plug-in version 3.1.0 and later supports VMware vSAN HCI Mesh feature for block volumes on vSphere version 7.0 Update 3 and later.Using vSphere Container Storage Plug-in on vSAN Max Deployments vSphere Container Storage Plug-in version 3.3.0 and later supports VMware vSAN Max deployments on vSphere version 8.0 Update 3 and later. vSAN Max is a new storage offering that provides Petabyte scale disaggregated storage for vSphere clusters. vSAN Max is powered by the vSAN Express Storage Architecture, also called ESA. vSAN Max provides an ability to deploy a highly scalable storage cluster that can be used as primary storage for vSphere clusters. Volume Snapshot and Restore vSphere Container Storage Plug-in supports the volume snapshot and restore capabilities. You can use a snapshot to provision a new volume, pre-populated with the snapshot data. You can also restore the existing volume to a previous state represented by the snapshot.Collecting Metrics with Prometheus to Monitor vSphere Container Storage Plug-in vSphere Container Storage Plug-in metrics. You can then visualize these metrics with Grafana dashboards to monitor health and stability of vSphere Container Storage Plug-in .Collect vSphere Container Storage Plug-in Logs kubectl logs to collect logs for vSphere Container Storage Plug-in pods. You can then analyze the logs to diagnose problems with your vSphere Container Storage Plug-in environment.
