<p>I use helm and I have a problem, when a pod (statefulset) is entring to <code>CrashLoopBackOff</code>, it never exit this state.</p>
<p>Even when there is a new rolling update, the statefulset still in the same state <code>CrashLoopBackOff</code> from the old rolling update.</p>
<h2>Question</h2>
<p>What can I do to force the statefulset to start the new rolling update (or even better, gracefully)?</p>
<ul>
<li>An answer for k8s-deployment will also be great!</li>
</ul>

Stav Alfi
<p>You can force helm to recreate resources by adding <code>--force</code> to the switches, for example</p>
<pre><code>helm upgrade --install -n mynamespace --force myrelease ./mychart
</code></pre>
<p>This will delete and recreate the resources, including the statefulset pods. This <em>may</em> (YMMV) fix your problem, it may not. It depends on that cause of the crashloop, so you should ideally fix that before even considering forcing a new rolling update. Or at least patch the statefulset so it's running correctly, before doing the update.</p>
