title: Kubernetes rescheduling of pods after a node becomes unreachable
body: <p>The example of <a href="https://kubernetes.io/docs/tutorials/stateful-application/zookeeper/" rel="nofollow noreferrer">running ZooKeeper in Kubernetes</a> shows how pods can be rescheduled on different nodes following a node being drained from connections, typically because maintenance has to be performed on it.</p>
  
  <p>The pods are rescheduled with the same identity that they have before, in this case the <code>myid</code> ZooKeeper servers, corresponding to the incremental number of each pod <code>zk-0</code>, <code>zk-1</code> and so on.</p>
  
  <p>If a node is not responding (possibly due to overload or a network problem), is it possible for Kubernetes to reschedule a pod on another node while the original pod is still running?</p>
  
  <p>It seems <a href="https://github.com/kubernetes/kubernetes/issues/27427" rel="nofollow noreferrer">some of this behavior has been specified explicitly</a>, but I don't know how to verify it short of setting up multiple nodes on a cloud provider and trying it.</p>