-
Notifications
You must be signed in to change notification settings - Fork 220
Add annotation to disable decryption on a per object basis #1549
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
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.
Some (very) important changes in the docs structure, then it looks good 👍
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.
LGTM! 🚀
|
Please squash all commits into one |
Signed-off-by: danhubern <[email protected]>
Done, is there anything else I have to do? |
|
Thanks @danhubern This will be shipped with Flux v2.8 in Feb 2026 |
As discussed in fluxcd/flux2#5612, this PR implements the
kustomize.toolkit.fluxcd.io/decryptannotation to disable decryption on a per object basis. This is necessary if decryption happens in the cluster at some later point in time, e.g. forSopsSecrets.