-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add content: "handling Secrets with GitOps" #88
Comments
I could definitely see that discussion turning into a blog post and that blog post then getting whittled down to a concise document. If anyone wants to collab on such a thing for the OpenGitOps Blog, please let me know. |
I am interested in helping on this @chris-short |
Would also love to help on this since k8s secrets management is something new for me. Go for it @mateuszpruchniak first! :) Excited to see what you will write! |
What is the status of this? |
Just sent you the doc. Currently stalled but maybe worth bringing up at next meeting? |
@scottrigby I noticed from last week’s meeting recording (which I unfortunately missed) that this is something we’re aiming to work on. I’d be happy to take the lead on it and either start a draft or build on what's already been done to help move this forward. |
Turn this into a work product, for example a blog post.
If we want this to be a document we can move to the docs repo, etc.
Discussed in open-gitops/project#96
Originally posted by chris-short March 16, 2022
Handling secrets with GitOps is becoming a frequent question and starting to become a problem. Some secrets solutions like sops and external-secrets are in various states of decay.
Luckily, this is in alpha and I feel like this will be our future answer: https://secrets-store-csi-driver.sigs.k8s.io/getting-started/installation.html
Despite being alpha, the Big 3 cloud providers (AWS, Azure, GCP and bonus, Hashicorp Vault) all have providers.
The text was updated successfully, but these errors were encountered: