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
kube-master-installation: improve systemd cross-unit robustness. #101176
Conversation
Hi @jkh52. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/retest |
@jkh52: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/hold I have concerns (raised internally). |
Also some minor reliability tweaks.
Latest snapshot removes the reboot (there are some cons) and vastly increases the retry interval. |
/unhold |
/ok-to-test |
/approve /retest /triage accepted |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jkh52, wojtek-t 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 |
Also some minor reliability tweaks.
What type of PR is this?
/kind bug
What this PR does / why we need it:
We have seen sometimes that if metadata service is flaky and kube-master-installation unit fails, downstream may still try and fail (such as kube-master-configuration). Our normal health signal based repair waits a very long time, so you can have a failed but idle master node for some time.
This adds more clear dependency between units, and immediately reboots the machine if kube-master-installation.service fails (much faster than otherwise).
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: