External Secrets

The External Secrets Kubernetes 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.

⚠️ Please bear in mind

While this project is not ready, you might consider using the following:

• Kubernetes External Secrets
• Secrets Manager
• External Secrets Operator

Installation

Clone this repository:

git clone https://github.com/external-secrets/external-secrets.git

Install the Custom Resource Definitions:

make install

Run the controller against the active Kubernetes cluster context:

make run

Apply the sample resources:

kubectl apply -f config/samples/external-secrets_v1alpha1_secretstore.yaml
kubectl applt -f config/samples/external-secrets_v1alpha1_externalsecret.yaml

We will add more documentation once we have the implementation for the different providers.

Planned Features

• Support to multiple Provider stores (AWS Secret Manager, GCP Secret Manger, Vault and more) simultaneously.
• Multiple External Secrets operator instances for different contexts/environments.
• A custom refresh interval to sync the data from the Providers, syncing your Kubernetes Secrets up to date.
• Select specific versions of the Provider data.

Kicked off by