secrets-store-csi-driver-provider-azure: failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

Followed directions from https://github.com/Azure/secrets-store-csi-driver-provider-azure#usage Installed fresh today on a new cluster (v1.17.5 via Rancher) with: helm install csi-secrets-store-provider-azure/csi-secrets-store-provider-azure --generate-name (also tried: helm install csi-secrets-store secrets-store-csi-driver/secrets-store-csi-driver kubectl apply -f https://raw.githubusercontent.com/Azure/secrets-store-csi-driver-provider-azure/master/deployment/provider-azure-installer.yaml Identical results) All the pods deploy fine I created Service Principle and installed as secret as directed
Deployed provider class https://github.com/kubernetes-sigs/secrets-store-csi-driver/blob/master/test/bats/tests/azure_synck8s_v1alpha1_secretproviderclass.yaml (updated appropriate values) The applied the example https://github.com/kubernetes-sigs/secrets-store-csi-driver/blob/master/test/bats/tests/nginx-deployment-synck8s-azure.yaml (nginx as container) nginx pod stuck on ContainerCreating, reporting Warning FailedMount 7s (x7 over 39s) kubelet, temp2-2 MountVolume.SetUp failed for volume “secrets-store-inline” : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

What did you expect to happen: Create pod and sync secrets as described by docs

Which access mode did you use to access the Azure Key Vault instance: Service Principal

Environment: Add defaults as of 5/14/2020

• Secrets Store CSI Driver version: (use the image tag):
• Azure Key Vault provider version: (use the image tag):
• Kubernetes version: (use kubectl version):
• Cluster type: (e.g. AKS, aks-engine, etc):