When you start a Pod on a cluster, it is scheduled on a specific node of the cluster. If the node, at a given moment, is not able to continue to host this Pod, the Pod will not be restarted on a new node – the application is not self-healing.
Let’s have a try, on a cluster with more than one worker (e.g., on the cluster installed in Chapter 1).
First, run a Pod; then examine on which node it has been scheduled:
$ kubectl run nginx --image=nginx
pod/nginx created
$ kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE ...
