<p>I found in my pod that if a container fails or is killed due to failing liveness probe, the container is restarted, but the pod is not.</p>

<p>This means that <code>initContainers</code> are not run again in a case of a crashed container.</p>

<p>In my case, I do need to run one of the <code>initContainers</code> every time the main container fails.</p>

<p>Is this possible? Am I missing something?</p>

<p>Currently, this is simply not supported: <code>livenessProbe</code> is a <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes" rel="nofollow noreferrer">"container level" probe</a> and if this probe fails only the said container is restarted, not the whole Pod</p>

<p>Though, you'll be glad to know that this behaviour is currently being implemented on this PR: <a href="https://github.com/kubernetes/community/pull/2342" rel="nofollow noreferrer">https://github.com/kubernetes/community/pull/2342</a>.</p>

<p>As a workaround before it's done and you eventually update, you'd have to rethink why you really need your <code>initContainers</code> in the first place, and consider a different co-ordination between your pod containers (be they initContainers or not) through a shared volume or some other scenarios depending on your use case.</p>
