You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
Verified etcd3 does allow each member to recover from its snapshot "when in an initial cluster bootstrapping process", where etcd2 does not.
We still need cluster runtime reconfiguration, which I wanted to avoid in the first place, to recover from a partial permanent failures of nodes up to N/2 but this is the same as etcd2.
ref kubernetes/kubernetes#22448
Notes:
etcdctl
should have an env varETCDCTL_API=2
orETCDCTL_API=3
provided to talk with an etcd cluster in API v2 or v3 respectively.kube-apiserver
talks with an etcd cluster in API v3 when--storage-backend etcd3
is provided.The text was updated successfully, but these errors were encountered: