• Lubomir I. Ivanov's avatar
    kubeadm: run MemberAdd/Remove for etcd clients with exp-backoff retry · bc74ac3e
    Lubomir I. Ivanov authored
    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.
    bc74ac3e
Name
Last commit
Last update
..
clicheck Loading commit data...
cloud-controller-manager Loading commit data...
controller-manager Loading commit data...
gendocs Loading commit data...
genkubedocs Loading commit data...
genman Loading commit data...
genswaggertypedocs Loading commit data...
genutils Loading commit data...
genyaml Loading commit data...
hyperkube Loading commit data...
importverifier Loading commit data...
kube-apiserver Loading commit data...
kube-controller-manager Loading commit data...
kube-proxy Loading commit data...
kube-scheduler Loading commit data...
kubeadm Loading commit data...
kubectl Loading commit data...
kubelet Loading commit data...
kubemark Loading commit data...
linkcheck Loading commit data...
BUILD Loading commit data...
OWNERS Loading commit data...