External Secrets
External Secrets Operator reads secrets from external secret management systems and writes them into Kubernetes Secrets on your cluster. Edka deploys it as a Helm chart in the external-secrets namespace with CRDs installed. Secrets stay in the external provider and never land in Git.
- Reads from AWS Secrets Manager, Azure Key Vault, Google Secret Manager, HashiCorp Vault, Doppler, and 1Password
- Keeps Kubernetes Secrets in sync as the source values change
- Templating for complex secret structures and transformations
- Namespace-level isolation for multi-tenant clusters
Features available
Connect a secret store and sync secrets from the cluster Secrets page, or create SecretStore, ClusterSecretStore and ExternalSecret resources through GitOps. The operator runs on your own cluster and tracks sync status per ExternalSecret. See the External Secrets docs.
Deploy External Secrets
External Secrets
Security
Securely sync your secrets from external providers like AWS Secrets Manager, Vault, GCP Secret Manager and more, directly to your Kubernetes cluster.