Add default values to the webhook configuration #2
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.
Motivation
Same as in the eumel8/cosignwebhook#64 - using GitOps agents who rely heavily on helm (like Rancher's fleet) creates a discrepancy between the created validatingwebhookconfiguration of a cluster and the expected manifest, as rendered via the helm templating engine.
Since a couple of fields are missing, the monitored GitOps resource is never reconciled, as it's always in a modified state.
This PR adds the "missing" fields, which are sensible defaults.
Tests done
Runs like this in 30+ k8s clusters in our internal CaaS plattform :)
Impact
Updating will unfortunately cause a redeployment of the webhook server. Other than that, nothing major happened,