No Description

Lucas Severo Alves 4661538d3c Use only amd64 for now 5 years ago
.github 4661538d3c Use only amd64 for now 5 years ago
api bea6994f42 fix: remove unneeded SetProvider func 5 years ago
assets 52fc65aeef Bootstrap project 5 years ago
config 364f6be071 Merge pull request #9 from external-secrets/feat/provider-interface 5 years ago
controllers ffd4a220d1 chore: remove newlines from license boilerplate 5 years ago
hack ffd4a220d1 chore: remove newlines from license boilerplate 5 years ago
pkg f1fb6cfa06 feat: implement provider interface 5 years ago
.gitignore 52fc65aeef Bootstrap project 5 years ago
Dockerfile 52fc65aeef Bootstrap project 5 years ago
LICENSE 59a364e04d initial commit 5 years ago
Makefile 0fce597e54 chore: upgrade controller-gen to 0.4.1 5 years ago
PROJECT fe86491c76 Change CRD subdomain from external-secerets.x-k8s.io to external-secrets.io 5 years ago
README.md b9926d2062 Fix typo 5 years ago
go.mod f1fb6cfa06 feat: implement provider interface 5 years ago
go.sum f1fb6cfa06 feat: implement provider interface 5 years ago
main.go ffd4a220d1 chore: remove newlines from license boilerplate 5 years ago

README.md

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:

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