mirror of https://github.com/k3s-io/k3s
bc74ac3eaa
When adding a new etcd member the etcd cluster can enter a state of vote, where any new members added at the exact same time will fail with an error right away. Implement exponential backoff retry around the MemberAdd call. This solves a kubeadm problem when concurrently joining control-plane nodes with stacked etcd members. From experiment, a few retries with milliseconds apart are sufficient to achieve the concurrent join of a 3xCP cluster. Apply the same backoff to MemberRemove in case the concurrent removal of members fails for similar reasons. |
||
|---|---|---|
| .. | ||
| clicheck | ||
| cloud-controller-manager | ||
| controller-manager | ||
| gendocs | ||
| genkubedocs | ||
| genman | ||
| genswaggertypedocs | ||
| genutils | ||
| genyaml | ||
| hyperkube | ||
| importverifier | ||
| kube-apiserver | ||
| kube-controller-manager | ||
| kube-proxy | ||
| kube-scheduler | ||
| kubeadm | ||
| kubectl | ||
| kubelet | ||
| kubemark | ||
| linkcheck | ||
| BUILD | ||
| OWNERS | ||