<p>When a Kubernetes pod goes into <code>CrashLoopBackOff</code> state, you will fix the underlying issue. How do you force it to be rescheduled?</p>

<p>For apply new configuration the new pod should be created (the old one will be removed).</p>
<ul>
<li><p>If your pod was created automatically by <code>Deployment</code> or <code>DaemonSet</code> resource, this action will run automaticaly each time after you update resource's yaml.
It is not going to happen if your resource have <code>spec.updateStrategy.type=OnDelete</code>.</p>
</li>
<li><p>If problem was connected with error inside docker image, that you solved, you should update pods manually, you can use <a href="https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/" rel="noreferrer">rolling-update</a> feature for this purpose, In case when new image have same tag, you can just remove broken pod. (see below)</p>
</li>
<li><p>In case of node failure, the pod will recreated on new node after few time, the old pod will be removed after full recovery of broken node. worth noting it is not going to happen if your pod was created by <code>DaemonSet</code> or <code>StatefulSet</code>.</p>
</li>
</ul>
<p>Any way you can manual remove crashed pod:</p>
<pre><code>kubectl delete pod &lt;pod_name&gt;
</code></pre>
<p>Or all pods with <code>CrashLoopBackOff</code> state:</p>
<pre><code>kubectl delete pod `kubectl get pods | awk '$3 == &quot;CrashLoopBackOff&quot; {print $1}'`
</code></pre>
<p>If you have completely dead node you can add <code>--grace-period=0 --force</code> options for remove just information about this pod from kubernetes.</p>
