<p>We started to monitor docker events in our k8s cluster and noticed that are a lot of <code>Kill/Die/Stop/Destroy</code> for various containers in a short time period.</p>

<p>Is that normal? (I assume it's not)</p>

<p>Aparently is not a capacity problem:</p>

<pre><code>Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  OutOfDisk        False   Thu, 16 Aug 2018 11:19:30 -0300   Tue, 14 Aug 2018 14:02:37 -0300   KubeletHasSufficientDisk     kubelet has sufficient disk space available
  MemoryPressure   False   Thu, 16 Aug 2018 11:19:30 -0300   Tue, 14 Aug 2018 14:02:37 -0300   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Thu, 16 Aug 2018 11:19:30 -0300   Tue, 14 Aug 2018 14:02:37 -0300   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Thu, 16 Aug 2018 11:19:30 -0300   Fri, 11 May 2018 16:37:48 -0300   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Thu, 16 Aug 2018 11:19:30 -0300   Tue, 14 Aug 2018 14:02:37 -0300   KubeletReady                 kubelet is posting ready status
</code></pre>

<p>All Pods shows status "Running"</p>

<p>Any tips on how debug it further?</p>

Heron Rossi
<p>You can inspect the docker container status as following commands on the node hosts where runs pods on.</p>

<pre><code>docker inspect &lt;container id&gt;
</code></pre>

<p>More option is <a href="https://docs.docker.com/engine/reference/commandline/inspect/" rel="nofollow noreferrer">here</a></p>

<p>And events logs and journal logs are helpful to debug.</p>

<pre><code>kubectl get events

journalctl --no-pager 
</code></pre>
