Restoring the master control plane after a loss of all masters in a Tectonic cluster in AWS

Updated 2019-07-09T15:32:50+00:00

Tectonic clusters contain three distinct types of nodes:

  1. master node(s) which carry the master control plane and core Kubernetes components (such as the scheduler or the api controller).
  2. worker node(s) which carry the user applications
  3. etcd node(s) which acts as a key-value storage for the cluster.

In a normal production environment, master nodes are usually run in HA (high availability) mode, so that the control plane is available at any given time, even in the event of a master failure. In this article, I'll explain and provide troubleshooting tips on how to rescue a Tectonic cluster with all masters down.

Subscriber content preview. For full access to the Red Hat Knowledgebase, please log in.

Not a subscriber? Learn more about the benefits of Red Hat Subscriptions.