Ross ROSS = Recommend OSS · open-source software intelligence for agents

kubernetes-sigs/secrets-store-csi-driver

Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume. observed · 2026-08-28

github.com/kubernetes-sigs/secrets-store-csi-driver · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

86/100

  • Activity 94
  • Release rhythm 69
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 59.5
  • age_days: 2800
  • days_rel: 126
  • days_push: 39
  • n_releases_24m: 11

Full methodology

Adoption not part of the score

1557 stars · 331 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A Kubernetes CSI driver that mounts secrets, keys, and certificates from external secrets stores (Vault, Azure Key Vault, AWS Secrets Manager, GCP Secret Manager, and others) into pods as volumes. It is a Kubernetes SIG Auth subproject configured via SecretProviderClass custom resources, with optional syncing to Kubernetes Secrets and auto-rotation.

Use cases

  • mount vault secrets into kubernetes pods
  • use azure key vault secrets in kubernetes containers
  • mount aws secrets manager values as pod volumes
  • sync external secrets store content into kubernetes secrets
  • auto-rotate mounted secrets in kubernetes
  • inject certificates and keys into pods from enterprise secret stores
  • avoid storing secrets in kubernetes etcd

When to choose

  • you run workloads on Kubernetes and use an external secrets store like Vault, Azure Key Vault, AWS Secrets Manager, or GCP Secret Manager
  • you want secrets mounted as files in pods rather than stored as Kubernetes Secrets
  • you need pod portability across providers via SecretProviderClass
  • you want automatic rotation of mounted secret content

When to avoid

  • you only need simple secrets stored natively in Kubernetes without external stores
  • you are not running Kubernetes
  • you need a secrets store itself rather than an integration driver
  • you need alpha features like rotation or secret syncing without accepting upgrade churn

Facets

service · maturity stable

secrets-management security container-orchestration deployment security cloud-computing self-hosted windows go cloud self-hosted csi-driver kubernetes hashicorp-vault azure-keyvault aws-secrets-manager gcp-secret-manager secret-rotation helm-chart sig-auth containers devops docker linux

7 sources

Member repositories

RepositoryRoleHealth v2
kubernetes-sigs/secrets-store-csi-drivermain86

For agents

markdown · JSON · MCP: product_card(name="kubernetes-sigs/secrets-store-csi-driver")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem