Add policy exception so that controller can be deployed in bootstrap mode (uses host network) #1215
Conversation
This file contains 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
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.
I found app-operator to fail installation during MC creation, during which we use bootstrap mode (and thus the host network which is disallowed by default Kyverno policies). I'm using a very similar solution to https://github.com/giantswarm/chart-operator/blob/master/helm/chart-operator/templates/policy-exceptions.yaml. Successfully tested manually by continuing the
mc-bootstrapMC creation procedure with app-operator version overridden with my change and the test catalog.Checklist