Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how are people handling secrets required by argo-cd? #492

Open
chupacabra71 opened this issue Jul 19, 2023 · 1 comment
Open

how are people handling secrets required by argo-cd? #492

chupacabra71 opened this issue Jul 19, 2023 · 1 comment

Comments

@chupacabra71
Copy link

I am using SSO via Authentik and it works great, but... i need to provide clientID and clientSecret values to dex for that connection to work. For all my other secrets, i use external-secrets-operator to read them from Vault, but since my operator is not ready during bootstrapping, i end up having to leave these values in my git repo. what are people doing to handle secrets needed during bootstrapping?

@todaywasawesome
Copy link
Contributor

@chupacabra71 We're using a lot of sealed secrets for that but external secrets with vault is excellent. You just have to make sure it gets bootstrapped too. It shouldn't be an issue if things start out of order as long as the secrets are eventually available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants