Additional documentation on kustomize patches with sops #2200
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
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.
As per @stefanprodan 's ask adding the chapter here instead of the Kustomization guide. See: fluxcd/kustomize-controller#1394