-
Notifications
You must be signed in to change notification settings - Fork 220
Additional documentation on kustomize patches with sops #1394
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
Conversation
047cc37 to
a70b30c
Compare
|
Hey @vlasov-y would you have time to review this PR? 🙏 I think it's a bit related to what you worked on recently? Thanks!!! 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once these comments are changed, it is clear to go and merge. Thanks @nagygergo!
matheuscscp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks very much you both!!! 🙏
Signed-off-by: Gergely Nagy <[email protected]>
88f9a21 to
8470ddf
Compare
| metadata: | ||
| name: secret | ||
| stringData: | ||
| publicConifg: "my-public-config" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think Flux docs should tell users to leave Secrets in plain text in the repo. I think the base Secret should contain no keys.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that apply to the "Kustomize secretGenerator" chapter as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we tell people to leave secrets in plain text in that chapter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, put the comment in the wrong place... My question was directed at this comment.
A better place for this documentation is here: https://fluxcd.io/flux/guides/mozilla-sops/
@nagygergo please copy the section from this PR into https://github.com/fluxcd/website/edit/main/content/en/flux/guides/mozilla-sops.md
|
A better place for this documentation is here: https://fluxcd.io/flux/guides/mozilla-sops/ @nagygergo please copy the section from this PR into https://github.com/fluxcd/website/edit/main/content/en/flux/guides/mozilla-sops.md |
Does that apply to the "Kustomize secretGenerator" chapter as well? |
This applies to what's in this PR. I'm not suggesting deleting anything from the current docs. |
|
Closing in favor of fluxcd/website#2200 as @stefanprodan asked. |
Adding some documentation on how Kustomize controller works with patch files and sops decryption. There is a mention of something like this in the SOPS user guide (https://fluxcd.io/flux/guides/mozilla-sops/#sops-encrypted_regex-conflict), but probably it is also good to describe both cases (secretsGenerator and patchfiles) in the kustomize controller, besides each other.