Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Replace a failed manager node

This section describes how to replace a failed manager node in your MOSK deployment. The procedure applies to the manager nodes that are, for example, permanently failed due to a hardware failure and remain in the NotReady state.

Note

If your cluster is deployed with a compact control plane, follow the Replace a failed controller node procedure.

To replace a failed manager node:

  1. Verify that the affected manager node is in the NotReady state:

    kubectl get nodes <CONTAINER-CLOUD-NODE-NAME>

    Example of system response:

    NAME                          STATUS     ROLES    AGE   VERSION
<CONTAINER-CLOUD-NODE-NAME>   NotReady   <none>   10d   v1.18.8-mirantis-1

  2. Delete the affected manager node as described in Delete a cluster machine.

  3. Add a manager node as described in Add a machine.

  4. Strongly recommended. Back up MKE as described in Mirantis Kubernetes Engine documentation: Back up MKE.

    Since the procedure above modifies the cluster configuration, a fresh backup is required to restore the cluster in case further reconfigurations fail.