🌱 Certwatcher: Don't require leaderelection #3273
Merged
+13
−0
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.
Controller-Runtime starts the certwatcher in the webhook server, which means it always runs regardless of the current replica being leader or not.
It turns out that kubebuilder adds it to the manager and as a result, it only runs on leader replicas. Make it a
LeaderElectionRunnable
and don't require leader election so that it will work correctly even if other projects use it in ways that were not originally anticipated.