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
Automated cherry pick of #90645: kubeadm: fix flakes when performing etcd MemberAdd on slower #91080
Automated cherry pick of #90645: kubeadm: fix flakes when performing etcd MemberAdd on slower #91080
Conversation
In slower setups it can take more time for the existing cluster to be in a healthy state, so the existing backoff of ~50 seconds is apparently not sufficient. The client dial can also fail for similar reasons. Improve kubeadm's join toleration of adding new etcd members. Wrap both the client dial and member add in a longer backoff (up to ~200 seconds). This particular change should be backported to the support skew. In a future change for master, all etcd client operations should be make consistent so that the etcd logic is in a sane state.
/kind bug |
Thanks @neolit123 for this fix. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, neolit123 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 |
/test pull-kubernetes-e2e-kind |
Cherry pick of #90645 on release-1.18.
#90645: kubeadm: fix flakes when performing etcd MemberAdd on slower
For details on the cherry pick process, see the cherry pick requests page.