<p>I have a Kubernetes cluster distributed on AWS via Kops consisting of 3 master nodes, each in a different AZ. As is well known, Kops realizes the deployment of a cluster where <strong>Etcd is executed on each master node</strong> through two pods, each of which mounts an EBS volume for saving the state. If you <strong>lose the volumes</strong> of <strong>2 of the 3</strong> masters, you automatically <strong>lose consensus</strong> among the masters. </p>

<p>Is there a way to use information about the only master who still has the status of the cluster, and <strong>retrieve the Quorum between the three masters</strong> on that state? I recreated this scenario, but the cluster becomes unavailable, and I can no longer access the Etcd pods of any of the 3 masters, because those pods fail with an error. Moreover, Etcd itself becomes read-only and it is impossible to add or remove members of the cluster, to try to perform manual interventions.</p>

<p>Tips? Thanks to all of you</p>

<p>This is documented <a href="https://docs.openshift.com/container-platform/3.11/admin_guide/assembly_restore-etcd-quorum.html" rel="nofollow noreferrer">here</a>. There's also another guide <a href="https://blog.containership.io/etcd" rel="nofollow noreferrer">here</a></p>

<p>You basically have to backup your cluster and create a brand new one.</p>
