External-secrets

External Secrets Operator is a Kubernetes operator that syncs secrets from external secret-management systems — such as HashiCorp Vault, AWS Secrets Manager,…

  • Infrastructure
  • Security
  • Tools & Utilities
External Secrets Operator is a Kubernetes operator that syncs secrets from external secret-management systems — such as HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Secrets Manager — into your cluster as native Kubernetes Secrets. It helps homelab and production teams keep credentials out of the cluster while workloads read them the normal way, so you can centralize and rotate secrets without committing them to Git or the cluster datastore.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 1 day ago
Popular
776,954 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
6,954
Open issues
381
Last commit
2026-11-20
Latest release
helm-chart-2.15.0
License
Apache-2.0
Activity
steady

Checked today - source: GitHub (external-secrets/external-secrets)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Make sure Docker works first Run docker run hello-world before deploying. It checks that Docker is installed and that your user can run containers, which avoids permission errors during setup. source
  • Point ExternalSecret at a store In the ExternalSecret, set secretStoreRef to the SecretStore (the setting that points to your vault) and set target.name. If those are missing or wrong, the controller doesn't know where to fetch secrets and the app can't get the credentials it needs. source
  • Give htpasswd the user pairs If you're generating an htpasswd file, provide key-value pairs like username: password for each account. Missing or misnamed pairs mean the generated htpasswd will lack users and logins will fail. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I control how often External Secrets updates a Kubernetes Secret?

Set spec.refreshInterval on the ExternalSecret to change the interval. Set spec.refreshPolicy to Periodic for regular updates or CreatedOnce to create the Secret only once.

How do I restrict who can read the secrets it syncs?

Use in-cluster RBAC to control access to the Kubernetes Secret objects. Also use store-level role limits to restrict access to the external secret store.

What resources do I create to connect External Secrets to an external provider?

Create ESO's custom API resources, ExternalSecret, SecretStore, and ClusterSecretStore. They provide a user-friendly abstraction over the external secret management API.

Can it sync revision-controlled secrets from an external vault?

Yes, it can sync revision-controlled secret data from an external vault into Kubernetes.

Answers sourced from discuss.kubernetes.io, external-secrets.io, external-secrets.io, www.reddit.com

Community

Collected 48 days ago - public community threads