fix: add background filter to restart trigger policies#95
Merged
thesuperzapper merged 1 commit intoFeb 5, 2024
Merged
Conversation
Signed-off-by: Mathew Wicks <[email protected]>
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.
This PR adds a precondition to filter out BACKGROUND events on our restart trigger policies.
This is needed because, in later versions of Kyverno, each
BACKGROUND_SCAN_INTERVALthe mutation will be applied, which will cause our deployments to restart erroneously.Note, that this behavior ONLY applies to "mutate existing" rules (which define
targets), so we don't need to update the other rules, like those that annotate the cloned secrets.