Not sure this is truly an issue with Rancher, seems like the cloud-provider should do this for you, but I know our users are going to trip over this.
To dynamically configure AzureFiles volumes, the provider/controller needs permissions to create a secret to store the share credentials in the namespace the pvc was created in.
The origin issue is https://github.com/rancher/rancher/issues/13947
Not sure this is truly an issue with Rancher, seems like the cloud-provider should do this for you, but I know our users are going to trip over this.
To dynamically configure AzureFiles volumes, the provider/controller needs permissions to create a secret to store the share credentials in the namespace the pvc was created in.
Related issues: https://github.com/kubernetes/kubernetes/issues/59543
Related documentation: The storageClass docs sort of mention that this is required as a side note. https://kubernetes.io/docs/concepts/storage/storage-classes/#azure-file
Rancher versions: rancher/rancher: v2.0.2