As a DevOps engineer, verify that the namespace you use for stateful services in the vSphere IaaS control plane environment has appropriate storage classes. The storage classes can be vSAN Shared-Nothing-Architecture (SNA) and vSAN Direct.
The
vSAN Data Persistence platform automatically creates these storage classes in the namespace after a vSphere administrator enables the stateful service. See
Enable Stateful Services in vSphere IaaS Control Plane.
Note: Only applications that run on the
Supervisor can use the vsan-direct and vsan-sna storage classes. These storage classes cannot be used inside a
TKG cluster.
In addition to default storage classes, vSphere administrator can also create custom storage policies and assign them to the namespace. See Create vSAN Direct Storage Policy and Create vSAN SNA Storage Policy.
Procedure
- ♦ Verify that the storage policies to be used with vSAN SNA and vSAN Direct are available in your namespace.
# kubectl get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE sample-vsan-direct-thick csi.vsphere.vmware.com Delete WaitForFirstConsumer true 3m36s sample-vsan-sna-thick csi.vsphere.vmware.com Delete WaitForFirstConsumer true 13m