Contact Free trial Login

Stop, Restart, or Update an Anypoint Private Cloud Edition Node

This topic describes the processes for removing an Anypoint Platform PCE node from active service, and returning it to service when ready.

Notes

To preserve your data in case of system failure, ensure that your system is backed up before attempting node maintenance.
The steps below must be performed on a single Anypoint Platform PCE node at a time. If maintenance is required on more than one node, the entire process must be completed on a single node before the next node is addressed.

Drain the Node

Before any maintenance or restart of a node can be performed, it must be removed from the cluster and its workload reassigned to the other nodes in the cluster.

  1. Check if the firewalld service is running and enabled:

    service firewalld status
  2. If firewalld is running, stop, disable, and mask it:

    sudo systemctl stop firewalld
    sudo systemctl disable firewalld
    sudo systemctl mask firewalld
  3. Retrieve the name of target node:

    kubectl get nodes
  4. Drain the node:

    kubectl drain --delete-local-data --ignore-daemonsets <node_name>
  5. Stop Gravity

    systemctl list-units | grep "planet-master"
      # note the full name of the Gravity "planet-master" unit
    systemctl stop <garvity_unit_name>

Apply Node Maintenance

Once the node has been drained and cordoned, any desired maintenance or a system reboot may be performed. Caution must be used, however, to avoid any updates to the system that violate the requirements of Anypoint Platform PCE.

Rejoin the Node

  1. Check Gravity Planet Master and Teleport status:

    systemctl list-units | grep gravity__gravitational
  2. If either Gravity service is not “loaded active running”, then enable it:

    systemctl enable <name_of_the_gravity_unit>
  3. Uncordon the node:

    kubectl uncordon <node_name>
  4. Verify cluster status:

    gravity status

    This command should show all nodes of the cluster with "healthy" status. Only after verifying that the node has rejoined the cluster and is in healthy status can the process be repeated for other nodes in the cluster.

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.