<p>I'm currently doing some tests on a kubernetes cluster.
I was wondering why the pods aren't rescheduled in some cases :</p>

<ul>
<li>When the node is unreachable</li>
<li>When the remote kubelet doesn't answer</li>
</ul>

<p>Actually the only case when a pod got rescheduled is when the kubelet notify the master.
Is it on purpose ? Why ?
If i shut down a server where there's a rc with a unique pod running, my service is down.</p>

<p>Maybe there's something i misunderstood.</p>

<p>Regards,
Smana</p>

<p>There is a quite long default timeout for detecting unreachable nodes and for re-scheduling pods, maybe you did not wait long enough? </p>

<p>You can adjust the timeouts with several flags:</p>

<ul>
<li>node-status-update-frequency on the kubelet (<a href="http://kubernetes.io/v1.0/docs/admin/kubelet.html" rel="nofollow">http://kubernetes.io/v1.0/docs/admin/kubelet.html</a>)</li>
<li>node-monitor-grace-period and pod_eviction_timeout on the kube-controller-manager (<a href="http://kubernetes.io/v1.0/docs/admin/kube-controller-manager.html" rel="nofollow">http://kubernetes.io/v1.0/docs/admin/kube-controller-manager.html</a>)</li>
</ul>
