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.
|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.|
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.
Check if the firewalld service is running and enabled:
service firewalld status
If firewalld is running, stop, disable, and mask it:
sudo systemctl stop firewalld sudo systemctl disable firewalld sudo systemctl mask firewalld
Retrieve the name of target node:
kubectl get nodes
Drain the node:
kubectl drain --delete-local-data --ignore-daemonsets <node_name>
systemctl list-units | grep "planet-master" # note the full name of the Gravity "planet-master" unit systemctl stop <garvity_unit_name>
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.
Check Gravity Planet Master and Teleport status:
systemctl list-units | grep gravity__gravitational
If either Gravity service is not “loaded active running”, then enable it:
systemctl enable <name_of_the_gravity_unit>
Uncordon the node:
kubectl uncordon <node_name>
Verify cluster status: