-
Notifications
You must be signed in to change notification settings - Fork 95
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
🐛 move the rebootstrap logic to registration agent #267
🐛 move the rebootstrap logic to registration agent #267
Conversation
/hold |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #267 +/- ##
==========================================
+ Coverage 61.06% 61.13% +0.06%
==========================================
Files 129 129
Lines 13771 13661 -110
==========================================
- Hits 8409 8351 -58
+ Misses 4588 4549 -39
+ Partials 774 761 -13
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
ee94897
to
fa91d13
Compare
fa91d13
to
f2c3e19
Compare
f2c3e19
to
cae4ce2
Compare
cae4ce2
to
e34e716
Compare
79a095d
to
9c13dac
Compare
9c13dac
to
b000388
Compare
5ed032f
to
4df38d3
Compare
4df38d3
to
d2993e8
Compare
4e04a07
to
085b461
Compare
Signed-off-by: Yang Le <[email protected]>
085b461
to
abfda59
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elgnay, 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 |
/unhold |
When the initial bootstrap hub kubeconfig is invalid, for example with wrong proxy settings, the bootstrap will not succeed and no hub kubeconfig will be created. Once a new bootstrap hub kubeconfig is provided by updating the bootstrap-kubeconfig-secret, the rebootstrapping will not be triggered because the klusterlet operator does not know if the bootstrap hub kubeconfig has changed.
By adding a new health checker, the agent will restart once bootstrap hub kubeconfig secret changes. That fix the issue described above. Another health checker is added as well to restart agent when the client certificate become expired.
Summary
Related issue(s)
Fixes #