<p>I am new to Kubernetes and want to ask two questions that may sound really basic.</p>
<ol>
<li>I understand that node controllers will monitor and respond to nodes' status. They will evict pods from unhealthy nodes. However, will the Kubernetes cluster make any effort to actively try to recover the unhealthy nodes or it will only wait for the human to recover the nodes manually?</li>
<li>If one container goes down in the cluster, will the cluster make any effort to actively try to recover it? I did some experiments in which I intentionally used the command &quot;docker stop &quot; to stop some of the containers (nginx-proxy, kube-controller-manager, kube-proxy). Those containers that I stopped didn't seem to come back automatically. Does the result indicate that containers that goes down in the cluster won't come back again until human starts to interfere?</li>
</ol>
<p>Thank you in advance.</p>

<ol>
<li><p>Basically answer is No!. Kubernetes cluster cannot make any effort to actively try to recover the unhealthy nodes. A node is a physical machine or virtual machine, now the responsibility of restarting a node or fixing a node when a node get unhealthy is on the admin.</p>
<ul>
<li><code>kubectl cluster-info dump</code>: To get complete information of cluster overall health</li>
<li><code>kubectl get nodes</code>: To see the available nodes, you can verify that all of the nodes you expect to see are present and that they are all in the Ready state.</li>
</ul>
</li>
<li><p>When i container failed then it also causes the pod failure. When a pod failed then kubernetes will restart the pod immediately. If you see the pod yaml by <code>kubectl get pods &lt;pod_name&gt; -o yaml</code> this command, you will see there is a portion named <code>ownerReferences</code> here the owener of the pod will be specified, basically they can be <code>ReplicaSet</code> or <code>StatefulSet</code> etc, they basically restart the pod when a pod failed (to maintain the desired number of pods). As the pods get restarted so the container also starts again, thus kubernetes try to fix the container failure.</p>
</li>
</ol>
