vSphere CSI Driver - v2.1.0 release
- CSI Migration for in-tree vSphere volumes on vSphere 7.0 Update 1. This feature requires upgrading Kubernetes to 1.19 release.
Minimum Kubernetes Version
- For vSphere CSI Migration feature the minimum Kubernetes version requirement is v1.19.0
Supported sidecar containers versions
- csi-provisioner - v2.0.0
- csi-attacher - v3.0.0
- csi-resizer - v1.0.0
- livenessprob - v2.1.0
- csi-node-driver-registrar - v2.0.1
vSphere CSI Driver issues
- When the static persistent volume with file-share is re-created with the same PV name, volume is not getting registered as a container volume with vSphere.
- Impact: attach/delete can not be performed on the such Persistent Volume.
- Workaround: wait for 1 hour before re-creating static persistent volume with file-share using the same name.
- Metadata syncer container deletes the volume physically from the datastore when Persistent Volumes with
Bound status and reclaim policy
Delete is deleted by the user when
StorageObjectInUseProtection is disabled on Kubernetes Cluster.
- Impact: Persistent Volumes Claim goes in the lost status. Volume can not be recovered.
- Workaround: Do not disable
StorageObjectInUseProtection and attempt to delete Persistent Volume directly without deleting PVC.
- Migrated in-tree vSphere volume deleted by in-tree vSphere plugin remains on the CNS UI.
- Impact: Migrated in-tree vSphere volumes deleted by in-tree vSphere plugin remains on the CNS UI.
- Workaround: Admin needs to manually reconcile discrepancies in the Managed Virtual Disk Catalog. Admin needs to follow this KB article - https://kb.vmware.com/s/article/2147750
- Volume expansion might fail when it is called with pod creation simultaneously.
- Impact: Users can resize the PVC and create a pod using that PVC simultaneously. In this case, pod creation might be completed first using the PVC with original size. Volume expansion will fail because online resize is not supported in vSphere 7.0 Update1.
- Workaround: Wait for the PVC to reach FileVolumeResizePending condition before attaching a pod to it.
- Deleting PV before deleting PVC, leaves orphan volume on the datastore.
- Impact: Orphan volumes remain on the datastore, and admin needs to delete those volumes manually using
- Upstream issue is tracked at: https://github.com/kubernetes-csi/external-provisioner/issues/546
- No workaround. User should not attempt to delete PV which is bound to PVC. User should only delete a PV if they know that the underlying volume in the storage system is gone.
- If user has accidentally left orphan volumes on the datastore by not following the guideline, and if user has captured the volume handles or First Class Disk IDs of deleted PVs, storage admin can help delete those volumes using
govc disk.rm <volume-handle/FCD ID> command.
- Filesystem resize is skipped if the original PVC is deleted when FilesystemResizePending condition is still on the PVC, but PV and its associated volume on the storage system are not deleted due to the Retain policy.
- Issue: https://github.com/kubernetes/kubernetes/issues/88683
- Impact: User may create a new PVC to statically bind to the undeleted PV. In this case, the volume on the storage system is resized but the filesystem is not resized accordingly. User may try to write to the volume whose filesystem is out of capacity.
- Workaround: User can log into the container to manually resize the filesystem.
- Volume cannot be resized in a Statefulset or other workload API such as Deployment.
- Recover from volume expansion failure.
- CNS file volume has a limitation of 8K for metadata.
- Impact: It is quite possible that we will not be able to push all the metadata to CNS file share as we need support a max of 64 clients per file volume.
- Workaround: None, This is vSphere limitation.