-
Notifications
You must be signed in to change notification settings - Fork 120
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
Migrate leader election to leases #711
Conversation
@acumino Thank you for your contribution. |
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.
Thanks for the PR!
IMO we can mark it ready for review - all MCM providers were released with the endpointsleases
resource lock.
We could also check whether the RBAC rules for endpoints can be now removed.
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.
/lgtm
@acumino , any comments on this one? |
There was not any specific RBAC for endpoints for leader election. I am not sure if mcm still need endpoints apart from the use for leader election if not we can drop it else not. |
That was the whole point of my comment - to check it :) I recall some cases when client-go or controller-runtime can try to list endpoints for the kubernetes service in the default namespace. At least we should be able to remove create/patch/update verbs for endpoints from the example RBAC. |
I have tested by removing the
There were no logs found stating cannot list |
Okay, my comment was to adapt the example RBAC and remove the |
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.
/lgtm
/kind enhancement
Which issue(s) this PR fixes:
Part of gardener/gardener#4742
Special notes for your reviewer:
/cc @ialidzhikov
Release note: