The External Secrets Operator reads information from a third party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
Multiple people and organizations are joining efforts to create a single External Secrets solution based on existing projects. If you are curious about the origins of this project, check out this issue and this PR.
- AWS Secrets Manager
- AWS Parameter Store
- Hashicorp Vault
- Google Cloud Secrets Manager
- Azure Key Vault
- IBM Cloud Secrets Manager
- Yandex Lockbox
- Gitlab Project Variables
- Alibaba Cloud KMS (Docs still missing, PRs welcomed!)
| Provider | Stability | Contact |
|---|---|---|
| AWS SM | alpha | ESO Org |
| AWS PS | alpha | ESO Org |
| Hashicorp Vault | alpha | ESO Org |
| GCP SM | alpha | ESO Org |
| Provider | Stability | Contact |
|---|---|---|
| Azure KV | alpha | @ahmedmus-1A @asnowfix @ncourbet-1A @1A-mj |
| IBM SM | alpha | @knelasevero @sebagomez @ricardoptcosta |
| Yandex Lockbox | alpha | @AndreyZamyslov @knelasevero |
| Gitlab Project Variables | alpha | @Jabray5 |
| Alibaba Cloud KMS | alpha | @ElsaChelala |
External Secrets Operator guides and reference documentation is available at external-secrets.io.
You can use GitHub's issues to report bugs/suggest features or use GitHub's discussions to ask for help and figure out problems. You can also reach us at our KES and ESO shared channel in Kubernetes slack.
Even though we have active maintainers and people assigned to this project, we kindly ask for patience when asking for support. We will try to get to priority issues as fast as possible, but there may be some delays.
We welcome and encourage contributions to this project! Please read the Developer and Contribution process guides. Also make sure to check the Code of Conduct and adhere to its guidelines.
Please report vulnerabilities by email to contact@external-secrets.io, also see our security policy for details.
