feat: kyverno policy for image-pull-secrets#47
Merged
thesuperzapper merged 1 commit intoOct 31, 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 adds a Kyverno ClusterPolicy which automatically replicates and injects Pod imagePullSecrets across the cluster.
This policy is primarily needed when using private container registries or for avoiding DockerHub pull limits.
As the new ClusterPolicy lives in the embedded Kyverno chart, we had to make some small changes to the
sync_argocd_apps.shscript. Previously, we were always force-syncing ClusterPolicies (withcloneorgeneratein the name), even if they were "missing" from the cluster, which caused a failure on the first sync, as this would result in the ClusterPolicy being applied before its CRD.