Andy Zhang

@mauriciopoppe the word `Breaking changes` may be incorrect, it actually does not block upgrade or usage since there is no API breaking change. Maybe it's better renaming as `Notion before...

marked as long-term since in current stage, we don't want to depend on AAD pod identity component since AAD pod identity also depends on cluster identity, it would makes the...

> Us too. It's silly that we have to use keys that are being phased out when this should just work with managed identities. @JohnGalt1717 there is `storeAccountKey` in storage...

> I tried that, but it still threw an error if the secret doesn't exist. If I provide storageAccount and and storeAccountKey = false, then it shouldn't check for anything...

looks like there is still no snapshot restore API: https://docs.microsoft.com/en-us/rest/api/storageservices/snapshot-share cc @RenaShahMSFT any progress on azure file snapshot API v2?

do you have the driver controller logs to share, follow https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/csi-debug.md#case1-volume-createdelete-issue

@rgr-ralf-it Are you using AKS? aks agent node does not support AAD domain join now, from CSI driver perspective, if node is domain joined, you could just append `-o domain=xxx`...

running following command should work, I think we could integrate with helm chart: ```console kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/windows/csi-proxy/csi-proxy.yaml ```

what is the pod namespace? the secret namespace should be same as pod namespace.

pls provide driver logs on the agent node: https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/csi-debug.md#case2-volume-mountunmount-failed