<p>If a node loses communication with the master, will it continue to run its workload in a self-healing way?</p>

<p>For instance, if the master is unavailable and a pod exceeds its cpu limit and is killed, will the node independently restart the pod because that pod has already been scheduled on the node?</p>

<p>Yes. The local (node) supervisor looking after your pods is the <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/" rel="nofollow noreferrer">kubelet</a> and while you can't change things while the connection to the API server is not available, the pods already scheduled on the node will continue to be supervised by the kubelet. In this context, an interesting but not super useful thing to know (for end-users) is that there are also so called <a href="https://kubernetes.io/docs/tasks/administer-cluster/static-pod/" rel="nofollow noreferrer">static pods</a> which you can launch manually, on the node.</p>
