Xing Yang

I see the following in the logs: vixDiskLib logs: ``` 2022-11-04T14:54:07.636Z| host-13| I005: DISKLIB-DSCPTR: : "ha-nfc://[vsanDatastore] 2f85df62-a08b-badd-ba23-bc97e1d50a70/_00a2/[email protected]:902" : Failed to open NBD extent. 2022-11-04T14:54:07.636Z| host-13| I005: DISKLIB-LINK : "ha-nfc://[vsanDatastore] 2f85df62-a08b-badd-ba23-bc97e1d50a70/_00a2/[email protected]:902"...

Can you take a look of step 3 here https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/main/docs/velero-vsphere-operator-user-manual.md#installing-velero-on-supervisor-cluster, did you create a configmap?

To support this, we need to handle the insecureSkipTLSVerify flag in the plugin code: https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/v1.4.0/pkg/utils/utils.go#L345.

This is not supported on Supervisor Cluster yet.

@sb-ev We are looking into this. We don't have a timeline yet.

At restore time, dynamic provisioning is used to create a new PVC. The destination datastore will be chosen based on the associated StorageClass (storage policy). Which StorageClass is used for...

@xinyanw409 Can you take a look?

@ywk253100 Can you provide links to the CVEs? We want to see what they are and the severity of them.

@ywk253100 As Xinyan said, we'll move datamgr into a separate go module if her current PR does not resolve the CVEs.

So we need to test backup/restore after making this change. @ywk253100 What Velero image can we test with? You don't have a Velero image that does not use base-debian yet,...