Divyen Patel
Divyen Patel
When I looked into this issue I observed two cases 1. When volume is not a CNS volume (temporary loss of volume from CNS DB). We are directly getting error...
We don't need to revert this change. for the case 2 mentioned [here](https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/2620#issuecomment-1781474630) If users intention is to delete the Claim and PV, and if disk (vmdk) is deleted from...
> cannot find UUID to disk path mapping. When this happens? How to produce this with user action?
@jingxu97 https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/2470 is protecting accidental deletion of CnsVSphereVolumeMigration CRs when volumes are on present in the vCenter CNS Cache. This fix will be there in v3.1.0 release.
v3.1.0 has the fix. Closing this Issue.
/remove-lifecycle rotten /reopen
@chethanv28 has enabled volume expansion for migrated volume with this PR - https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/2194 the feature should be available in the next release of the vSphere CSI Driver.
The vSphere CSI Driver has been upgraded with the addition of Multi vCenter support. You can access the latest release at https://github.com/kubernetes-sigs/vsphere-csi-driver/releases/tag/v3.0.0 and documentation can be found at https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/3.0/vmware-vsphere-csp-getting-started/GUID-8B3B9004-DE37-4E6B-9AA1-234CDA1BD7F9.html
/remove-lifecycle stale