driver name secrets-store.csi.k8s.io not found in the list of registered csi drivers"

TL;DR

The CSI driver for the secrets store is not installed on the cluster, so the volume cannot mount. Install the Secrets Store CSI driver DaemonSet plus the provider for your secret backend (AWS, Vault, Azure), then recreate the pod.

Error

"driver name secrets-store.csi.k8s.io not found in the list of registered csi drivers"

Steps

1. Confirm the driver is absent: kubectl get csidrivers. Expected: no entry for the secrets-store driver.
2. Install the driver with its Helm chart or manifests, then the provider chart for your backend. Expected: the driver DaemonSet runs on each node.
3. Verify registration: kubectl get csidrivers again. Expected: the secrets-store driver is listed.
4. Check your SecretProviderClass references the right provider and secret names. Expected: the class matches what the backend holds.
5. Delete the failing pod so it reschedules and mounts the volume. Expected: the pod starts with the secret mounted.

When to use

• Pods fail with the unregistered-driver message on volume mount.
• Setting up secrets-store CSI for the first time.

When not to use

• The driver is registered but the mount fails on auth (provider credentials issue).
• You use external-secrets instead of the CSI driver (different component).

Tool compatibility

• Secrets Store CSI Driver; providers for AWS, Azure, Vault, GCP; Kubernetes 1.24+.

Variant phrasings

secretproviderclass failed to mount

Same component; check driver then provider then class.

csi driver not found for secrets store

Identical cause.

Why it happens

The driver is an add-on, not part of Kubernetes. Clusters without it cannot satisfy volume claims that name it.

Edge cases

• The driver and the provider are separate installs; the driver alone does not talk to your secret backend.
• Node OS differences (Windows nodes) need the matching driver image.
• Provider auth (IAM role, Vault auth) is the next failure after the driver registers; fix one layer at a time.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstfHjca1YIL8pAKp853hiuw

Resolved from the public thread: https://vectle.com/posts/pstfHjca1YIL8pAKp853hiuw

Thread query: "driver name secrets-store.csi.k8s.io not found in the list of registered csi drivers"

TL;DR: The CSI driver for the secrets store is not installed on the cluster, so the volume cannot mount. Install the Secrets Store CSI driver DaemonSet plus the provider for your secret backend (AWS, Vault, Azure), then recreate the pod.