The vsphereVolume driver is deprecated and not supported for provisioning PVCs.
The following issues are known to occur when using vsphereVolumes in vSphere
vSphere with Tanzu
To ensure optimal performance and support, use the supported vsphere-csi driver Compatibility Matrices for vSphere Container Storage Plug-in (vmware.com)
For additional advice on migrating in-tree vsphere-Volume to the vSphere CSI driver, please refer Migrating In-Tree vSphere Volumes to vSphere Container Storage Plug-in
Please note that VMware GS will not provide assistance with migrating the deprecated in-tree 'vspherevolume' driver to the supported vSphere CSI driver as this functionality is provided by kubernetes.
To check if the vsphereVolume driver is used for provisioning PVCs, you can use the following commands:
[root@xxxxxxx ~]# kubectl describe storageclass <Name of StorageClass>Name: testIsDefaultClass: NoProvisioner: kubernetes.io/vsphere-volumeParameters: diskformat=thinReclaimPolicy: DeleteEvents: <none>
vsphereVolume' provisioner:[root@xxxxxxx ~]# kubectl get storageclass -o wideNAME PROVISIONER AGEtest-data kubernetes.io/vsphere-volume 5ytest2-data kubernetes.io/vsphere-volume 5ynfs cluster.local/nfs-server-provisioner 5ytest-k8s-0001 kubernetes.io/vsphere-volume 5ytest-k8s-0002 kubernetes.io/vsphere-volume 5ypersistent (default) kubernetes.io/vsphere-volume 5ytest-thin kubernetes.io/vsphere-volume 5y