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
Bug 1958885: Switch to client-go leader-with-lease election. #238
Bug 1958885: Switch to client-go leader-with-lease election. #238
Conversation
This is a backport of PR#229 into 4.7.
Previously, NTO relied on the operator-sdk (leader-for-life) way of
handling leader election. The leader-for-life was implemented by
relying on k8s garbage collector mechanism the same way as implemented
by operator-sdk. Unfortunately, practise shows (rhbz#1916865,
rhbz#1958885, rhbz#1962219) this is not reliable as the ConfigMap locks
are sometimes not garbage collected.
Therefore, switch to leader-with-lease election mechanism as provided by
the client-go package, which seems to be more reliable at this point.
Other changes:
- fix incorrect error reporting on metrics server shutdown
- fix default_irq_smp_affinity e2e test for systems with less then 4
CPUs
- go mod tidy
|
@jmencak: No Bugzilla bug is referenced in the title of this pull request. 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. |
|
@jmencak: This pull request references Bugzilla bug 1958885, which is invalid:
Comment 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. |
|
/bugzilla refresh |
|
@jmencak: This pull request references Bugzilla bug 1958885, which is invalid:
Comment 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. |
|
/bugzilla refresh |
|
@jmencak: This pull request references Bugzilla bug 1958885, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (skordas@redhat.com), skipping review request. 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. |
|
thanks @jmencak , |
/lgtm :| /joke |
|
@kpouget: Did you hear about the runner who was criticized? He just took it in stride 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmencak, kpouget 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 |
|
@jmencak: All pull requests linked via external trackers have merged: Bugzilla bug 1958885 has been moved to the MODIFIED state. 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. |
This is a backport of #229 into 4.7.
Previously, NTO relied on the operator-sdk (leader-for-life) way of handling leader election. The leader-for-life was implemented by relying on k8s garbage collector mechanism the same way as implemented by operator-sdk. Unfortunately, practise shows (rhbz#1916865, rhbz#1958885, rhbz#1962219) this is not reliable as the ConfigMap locks are sometimes not garbage collected.
Therefore, switch to leader-with-lease election mechanism as provided by the client-go package, which seems to be more reliable at this point.
Other changes:
go mod tidy