<p>Similar question on SO has 10 answers as 'force delete the pod' -_-</p>

<p>Of course this is unacceptable as it causes problems on the cluster - too many pods are stuck on 'terminating', and many times if you try to delete a random pod it also gets stuck. It happens fairly randomly.</p>

<p>So how to determine, first why are 'termination' commands issued and second how to find the culprit behind the freezes.</p>

<p>Is it the CNI? Core components like kubelet, controllermanager?</p>

<p>Logs don't show anything useful, nor does 'describe pod'.</p>

<p>If your pods got terminated with apparently no cause, it could be:</p>

<ul>
<li>the node is under stress (memory, cpu)  </li>
<li>liveness condition is not respected</li>
</ul>

<p>For these reasons, the scheduler kills some pods.</p>

<p>How to determine the precise cause? 
If you found 'logs' and 'describe' command useless, it could be useful a monitoring system (ex. influxdb+grafana:  <a href="https://github.com/kubernetes/heapster/tree/master/deploy/kube-config/influxdb" rel="nofollow noreferrer">https://github.com/kubernetes/heapster/tree/master/deploy/kube-config/influxdb</a>).</p>
