Stopping and starting Kubernetes cluster

To stop the servers or virtual machines running Kubernetes (for example, to take a VMWare snapshot), follow these instructions.

Stopping the Kubernetes cluster

To stop the cluster:

As the root user, stop all worker nodes, simultaneously or individually. For example, enter the following command to stop the Kubernetes worker nodes:
Note: If running in VMWare vSphere, use Shutdown Guest OS.
```
shutdown -h now
```
After all the worker nodes are shut down, shut down the Kubernetes master node.

Note: If the NFS server is on a different host than the Kubernetes master, you can shut down the Kubernetes master when you shut down the worker nodes.
Stop the NFS server next. By default, this is located on the Kubernetes master node and will be shutdown when the Kubernetes master node host or virtual machine is powered off.
Stop the server or virtual machine running the Docker registry last. The Docker registry is normally running on the Kubernetes Master node and will get stopped when the master node is powered off.

To restart or start the Kubernetes cluster, perform the following steps:

Start the Docker registry, normally the Docker registry is on the same node as the Kubernetes master and will get started automatically when the server or virtual machine is started that contains the Docker registry is started.
Start the NFS server and wait two minutes after the operating system has started before proceeding to ensure that the NFS server has started. Normally the NFS server is on the Kubernetes master and the NFS Server will start automatically when the server or virtual machine is started that contains the NFS Server.
If not already running, start the Kubernetes master and all worker nodes at the same time. If the Kubernetes master was already running, start all worker nodes at the same time or start the worker nodes individually in rapid succession.