HelmRelease Guide: Values Secret generated with Kustomize and SOPS #1165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I spent a couple of extra minutes to figure out what kind of |
|
Credit goes to @jseiser who worked out how to do this with a little bit of help in our Slack channel and Discussions pages 🎉 https://gist.github.com/jseiser/eed3b4ffdd1ff3def604c4c78c989c1f |
|
Squashing for review |
kingdonb
force-pushed
the
helmrelease-with-secret-generator
branch
from
553e1ff to
725ab99
Compare
kingdonb
force-pushed
the
helmrelease-with-secret-generator
branch
from
725ab99 to
fab97cd
Compare
kingdonb
pushed a commit
to kingdonb/bootstrap-repo
that referenced
this pull request
Sep 28, 2022
ref: fluxcd/website#1165 Signed-off-by: Kingdon Barrett <[email protected]>
pjbgf
approved these changes
Sep 28, 2022
pjbgf
reviewed
Sep 28, 2022
pjbgf
reviewed
Sep 28, 2022
kingdonb
force-pushed
the
helmrelease-with-secret-generator
branch
from
211e468 to
9c8f91f
Compare
kingdonb
force-pushed
the
helmrelease-with-secret-generator
branch
from
14daa1e to
07526bb
Compare
Addition to the HelmRelease Guide: Values from Secret with SOPS One more additional guide for HelmReleases with values that come from a SOPS encrypted secret. There are a few things to be aware of that make this not quite straightforward extrapolation from the ConfigMapGenerator example, I think this should be good to help more users from struggling. * show more complete example of .sops.yaml It's fine to use a different file name so we don't trigger the rule, but I don't want to avoid talking about `creation_rules` just because I don't know, don't want to guess what order they were matching. I looked it up, the first match is chosen, and `filename_regex` has been removed. Let's not impute that changing a filename to something other than .yaml is the only good way to skin the cat, I think people will prefer to learn and understand how to use their `.sops.yaml` instead of making up strange names to avoid matching the existing rule. Co-authored-by: Paulo Gomes <[email protected]> Signed-off-by: Kingdon Barrett <[email protected]> Use values.yaml as the input filename Signed-off-by: Kingdon Barrett <[email protected]>
kingdonb
force-pushed
the
helmrelease-with-secret-generator
branch
from
07526bb to
8295928
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One more additional guide for HelmReleases with values that come from a SOPS encrypted secret.
There are a few things to be aware of that make this not quite straightforward extrapolation from the ConfigMapGenerator example, I think this should be good to help more users from struggling. This has come up several times in Slack, we finally had a user who was persistent enough to discover all of the major tripping hazards and help me document them here.
We may want to let this one gather some reviews before it merges, I have tested it before writing, so strictly speaking this doc is not yet "tested" as in shown to work from a reading of the document, but the methods are tested and verified to work.
Thanks to our Slack community for helping us cover all our bases in the docs! 🌮 🎉