docs: update sync script to force update kyverno policies#40
Merged
thesuperzapper merged 1 commit intoOct 2, 2023
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 updates the
sync_argocd_apps.shscript so that it will automatically usekubectl replace --forcewith Kyverno ClusterPolicies that have a "generate" type rule.This is needed because Kyverno does not have a method for updating these policies/rules without deleting and recreating the whole ClusterPolicy: kyverno/kyverno#7718
We can remove this additional complexity once Argo CD adds the
argocd.argoproj.io/sync-options: Force=trueannotation, which allows us to use force syncing with only specific resources: argoproj/gitops-engine#414