Stop and Restart a Single-Node Deployment
On occasion, single-node TPI deployments must be stopped and restarted. One example of this is when you need to perform scheduled maintenance.
To stop and restart a single-node TPI Deployment:
- Login to the node as a user with administrator privileges.
- Find the name of the node. In the example within this topic, the node is named master3a.
# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master3a Ready master 30d v1.17.3
Drain the node.
# /bin/kubectl drain master3a --ignore-daemonsets --delete-local-data
Check that the node is in the “Ready,SchedulingDisabled” status.
# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master3a Ready,SchedulingDisabled master 27d v1.17.3
Stop or restart the server or VM.
Next, uncordon the node (i.e. make the node schedulable).
# kubectl uncordon master3a
Finally, ensure that the node is in the “Ready” status.
# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master3a Ready master 30d v1.17.3