Andy Zhang

do you have two PVs with same `volumeHandle` value?

pls don't use same volumeHandle value, if orignial PV is still used, and second PV with same volumeHandle value would not be mounted on the same node

if PV is created by the driver, then volumeHandle would be unique, the original problem is that the self configured PV is still mounted on the node, and there is...

it's related to this upstream issue: https://github.com/kubernetes/kubernetes/issues/91556, volumeHandle is the unique ID detected by kubelet when mount, so it's by design in k8s now. for dynamic case, the volumeHandle is...

it's fixed by https://github.com/kubernetes-sigs/azurefile-csi-driver/pull/1077, currently the fix is only on master branch, we will release v1.22.0 which has this fix.

> Hi, will this feature support cross tenant please? Can we have a sc from another subscription of another tenant? @nsu700 that depends on which cluster identity you are using....

close this issue since it's already supported in v1.22.0 version with cross subs support.

> Let me asked team to see if they can move to 1.25. Thanks. > > I wonder if the demo and probe use the same code base, if we...

@vibhansa-msft do you have any guidance about how to make unzip faster based on blobfuse v1 mount, like tuning some mount options?

this error message is actually a warning message in `TranslateInTreePVToCSI`: `could not get account name from , correct format: azure-storage-account-(.+)-secret` which is used to get volumeID with an account name....