-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable leader election for webhook #3863
Disable leader election for webhook #3863
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/kind bug |
/release-note-none |
@vincent-pli: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @imjasonh @afrittoli
SGTM
The webhook controller does use leader election, not the It's similar for all the other webhooks. They have an See also: #2735 (comment) |
@afrittoli this comment is great, can you propose it as official documentation in knative/pkg? I can definitely see other folks using that framework to have similar confusion. |
@afrittoli |
In
knative/pkg
,controller
leverageleader election
andbuckets
to support HA, butwebhook
has different approach, I meanwebhook
depends onhpa
andpdb
, so thewebhook
do not need anyleader election
, I mean do not need createlease
,Below is the case when I set
buckets: "3"
in config-leader-election.yaml, it's not make sense and useless.Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE