Course contentsShow
← Cloud and Infrastructure
Lesson 2276 of 2,98948. Secrets ManagementFree lesson

Secrets Store CSI Driver

Understand the Secrets Store CSI Driver for mounting secrets from external stores as Kubernetes volumes.

Secrets Store CSI Driver

You'll learn: How the Secrets Store CSI Driver bridges external secret stores with Kubernetes by mounting secrets directly as volumes using the native CSI interface.

What Problem Does It Solve?

You've seen the External Secrets Operator (which syncs secrets into Kubernetes Secrets) and Vault Agent Injector (which uses sidecars to inject secrets). The Secrets Store CSI Driver takes a different approach: it uses Kubernetes' Container Storage Interface (CSI) to mount secrets from external stores (like Vault, AWS Secrets Manager, or Azure Key Vault) directly as files in your pods—without creating Kubernetes Secret objects at all.

Think of it like a USB drive: instead of copying files from the drive to your computer's hard disk (External Secrets Operator), you read files directly from the mounted USB drive itself (CSI Driver).

How It Works

The CSI Driver architecture consists of:

  1. DaemonSet pods running on each node that handle the mount operations
  2. Provider plugins for each secrets backend (Vault, AWS, Azure, GCP)
  3. SecretProviderClass resources that define what to fetch and where to mount it
  4. Your application pods that reference these as volumes

When a pod starts, the CSI driver authenticates to your external store, retrieves the secrets, and presents them as files in the specified mount path. Secrets never persist as Kubernetes Secret objects (though you can optionally sync them if needed).

Key Benefits

  • Direct integration with external stores without intermediate Kubernetes Secrets
  • No sidecars required (unlike Vault Agent Injector)
  • Standard Kubernetes volume semantics your team already understands
  • Provider-agnostic interface across multiple secret backends

Key Takeaway: The Secrets Store CSI Driver mounts secrets from external stores as pod volumes using Kubernetes' native CSI framework, eliminating the need for Kubernetes Secret objects or sidecar containers while maintaining a standard volume interface.