-
Notifications
You must be signed in to change notification settings - Fork 97
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
🌱 enable leader election of klusterlet-agent on single node managed cluster #695
🌱 enable leader election of klusterlet-agent on single node managed cluster #695
Conversation
275a62f
to
c0fa479
Compare
c0fa479
to
1d6e452
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #695 +/- ##
=======================================
Coverage 63.37% 63.37%
=======================================
Files 185 185
Lines 17765 17765
=======================================
Hits 11258 11258
+ Misses 5577 5576 -1
- Partials 930 931 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
1d6e452
to
39b75b5
Compare
…sters Signed-off-by: Qing Hao <qhao@redhat.com>
39b75b5
to
81e8c59
Compare
/assign @elgnay @qiujian16 |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haoqing0110, qiujian16 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 |
8544ff1
into
open-cluster-management-io:main
…aged clusters (open-cluster-management-io#695)" This reverts commit 8544ff1. Signed-off-by: xuezhaojun <zxue@redhat.com>
Summary
The leader election of the klusterlet-agent is disabled on the single node managed cluster to speed up the restart procedure (open-cluster-management-io/registration-operator#193). While it might cause that two pods with different configuration, such as images or bootstrap config, running at the same time. Some unexpected behavior happens in this situation, for example, when old and new agents both exist, they override hub-kubeconfig-secret with different value and trigger each other create csr constantly.
To fix those issues, it is necessary to enable the leader election of the klusterlet-agent on the single node managed cluster.
Related issue(s)
Fixes #