<p>If Pod's status is <code>Failed</code>, Kubernetes will try to create new Pods until it reaches <code>terminated-pod-gc-threshold</code> in <code>kube-controller-manager</code>. This will leave many <code>Failed</code> Pods in a cluster and need to be cleaned up.</p>

<p>Are there other reasons except <code>Evicted</code> that will cause Pod <code>Failed</code>?</p>

<p>There can be many causes for the POD status to be <code>FAILED</code>. You just need to check for problems(if there exists any) by running the command</p>
<pre><code>kubectl -n &lt;namespace&gt; describe pod &lt;pod-name&gt;
</code></pre>
<p>Carefully check the <code>EVENTS</code> section where all the events those occurred during POD creation are listed. Hopefully you can pinpoint the cause of failure from there.</p>
<p>However there are several reasons for POD failure, some of them are the following:</p>
<ul>
<li>Wrong image used for POD.</li>
<li>Wrong command/arguments are passed to the POD.</li>
<li>Kubelet failed to check POD liveliness(i.e., liveliness probe failed).</li>
<li>POD failed health check.</li>
<li>Problem in network CNI plugin (misconfiguration of CNI plugin used for networking).</li>
</ul>
<p><br>For example:<br><br>
<a href="https://i.stack.imgur.com/VMHTf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VMHTf.png" alt="pod failed due to image pull error" /></a></p>
<p>In the above example, the image &quot;not-so-busybox&quot; couldn't be pulled as it doesn't exist, so the pod FAILED to run. The pod status and events clearly describe the problem.</p>
