Divyen Patel

@jingxu97 During our debugging session we observed that some of the feature gates were disabled in the v3.0.0 release you were using. Do you see this issue getting resolved on...

@lethargosapatheia Once you fix connectivity between vSpehre CSI Controller Pod and vCenter server, the issue regarding CSINodeTopology CRD is not found will be fixed.

basically, registration of CRD happens in the syncer container, and if it crashes before registering CRDs then Node Daemonset Pods will not be unable to create required CRD instances.

We will move the registration of CRs in the deployment YAML file so we do not have internal container dependencies while Pod is coming up. cc: @vdkotkar

/assign @vdkotkar

@vu3oim only key is needed in the label for `node-role-kubernetes-io-control-plane` https://kubernetes.io/docs/reference/labels-annotations-taints/#node-role-kubernetes-io-control-plane How are you deploying k8s cluster?

/remove-lifecycle rotten

Have you checked draining node is detaching volume from the Node VM using vSphere in-tree plugin? We have observed in the past that the in-tree vSphere plugin does not detach...

@gnufied if volumes are still attached to Node VM even after drain, it is not a migration issue. It is an in-tree driver issue. Do we know why the in-tree...

@gnufied another workaround we can try is to patch CnsVSphereVolumeMigration CR and set `ProtectVolumeFromVMDelete` in the `CnsVSphereVolumeMigrationSpec` as true. Refer to https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/pkg/apis/migration/v1alpha1/types.go#L41 This will skip calling API to set this...