-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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: use 'leases' as default resource lock object #1773
⚠ leaderelection: use 'leases' as default resource lock object #1773
Conversation
4f4d30e
to
d2c2839
Compare
/test pull-controller-runtime-test-master |
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
d2c2839
to
6c4d947
Compare
/test pull-controller-runtime-test-master |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: joelanford, 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 |
Update the default resource lock from
configmapsleases
toleases
.The previous default (since v0.7.0) was
configmapsleases
, which is the migration step fromconfigmaps
toleases
. Since the default wasconfigmapsleases
for over a year, spanning five minor releases, any actively maintained operators are very likely to have a released version that usesconfigmapsleases
. Therefore defaulting toleases
now should be safe.Any operators currently on a version <0.7.0 should migrate from
configmaps
toleases
viaconfigmapsleases
.configmaps
configmapsleases
.leases
.Operators currently using
configmaps
should:configmapsleases
when configuring leader election in this version)leases
when configuring leader election in this version)See kubernetes/kubernetes#107454 (This PR moves controller-runtime from step x+1 to x+2)
Signed-off-by: Joe Lanford joe.lanford@gmail.com