-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
✨LeaderElection configuration as flags #2664
✨LeaderElection configuration as flags #2664
Conversation
Hi @trutx. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Yes, I think we'd want to expose it for the KubeadmControlPlane controller manager as well Since the docker provider is mainly used for testing, I don't think there is any need to expose leader election configuration.
Same thing here, this provider should only be used during testing, so no need to expose leader election config here. |
/ok-to-test |
/assign |
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.
There are improvements discussed in the previous reviews that can be targeted as an add-on. Would you be able to file an issue for consolidating some kind of controller-runtime flag library we could share across controllers? Otherwise, one comment on the flag description and the rest lgtm
/milestone v0.3.2 |
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.
We'll also need an issue in CAPA and CAPV that adds these flags there as well. I'd be also helpful to add it to this document https://master.cluster-api.sigs.k8s.io/developer/providers/v1alpha2-to-v1alpha3.html for providers to implement in the same way
LGTM pending squash |
Co-Authored-By: Andrew Rudoi <[email protected]> Co-Authored-By: Roger Torrentsgeneros <[email protected]>
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: trutx, vincepri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Back from pseudo-holidays and all the work is done. Thanks y'all :D |
What this PR does / why we need it:
Enables setting manager LeaderElection options via command line flags
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #2653
I just implemented the optional settings in these two files but there's 3 other files where they could be implemented as well:
https://github.com/kubernetes-sigs/cluster-api/blob/master/controlplane/kubeadm/main.go
https://github.com/kubernetes-sigs/cluster-api/blob/master/test/infrastructure/docker/main.go
https://github.com/kubernetes-sigs/cluster-api/blob/master/cmd/example-provider/main.go
Do you think it makes sense to add the flags there too?