This topic provides the recommended configuration limits for vSphere Container Storage Plug-in. When you use vSphere Container Storage Plug-in in your environment, stay within the supported and recommended limits.
|Limits||Single Access Volume||Multi Access Volume|
|Number of volumes||
||100 file shares per vSAN cluster
100 concurrent clients for RWM PVs
|Number of RWO PVs, backed by virtual disks, per a VM with four controllers||Maximum 59
With four Paravirtual SCSI controllers on VM with one slot used for the primary disk of node VM.
|Multiple instances of vSphere Container Storage Plug-in pods in multi-node control plane environment||replica = 3||replica = 3|
- For higher availability, run vSphere CSI Controller with minimum of three replicas. If your Kubernetes cluster has more than three control plane nodes, set the CSI Controller replicas to match the number of control plane nodes on the cluster.
- If your development or test Kubernetes cluster does not contain multiple control plane nodes, set the replica to one.
- Limits for
Single Access Volumeare applicable to both single access file system volumes and single access block volumes.
- vSphere Container Storage Plug-in supports a single vCenter Server only. To use vSphere Container Storage Plug-in, ensure that node VMs do not spread across multiple vCenter Server instances. The datastore you use for provisioning volumes should not be mounted across multiple vCenter Server instances.
- vSphere Container Storage Plug-in uses only Paravirtual SCSI controllers to attach volumes to node VMs. Each non Paravirtual SCSI controller on the node VM reduces the maximum limit of RWO PVs per node VM by 15.