updaters: add toggle to deploy CRI hooks #197
Merged
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
The CRI hooks are unconditionally deployed, but that creates waste when the event-based notification mechanism is not enabled. We should expose a way to enable the callers to disable the deployment of CRI hooks to avoid unnecessary churn. Signed-off-by: Francesco Romani <[email protected]>
ffromani
force-pushed
the
rte-optional-hook
branch
from
72d1939 to
224d319
Compare
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.
The CRI hooks are unconditionally deployed, but that creates waste when the event-based notification mechanism is not enabled. We should expose a way to enable the callers to disable the deployment of CRI hooks to avoid unnecessary churn.