<p>I have a pod with a normal python container and istio running as a side car. During a redeployment, I see that one container start fine, the other does not.</p>
<pre><code>NAME                 READY   STATUS
my-pod-name-xyz      1/2     Running
</code></pre>
<p>The logs of both containers appear to be fine. In the description of the pod, I see the following event:</p>
<pre><code>  Warning  Unhealthy  97s   kubelet            Readiness probe failed: Get &quot;http://172.29.148.23:15021/healthz/ready&quot;: dial tcp 172.29.148.23:15021: connect: connection refused
</code></pre>
<p>How do I find out which container is failing?</p>

sigma1510
<p>The ReadinessProbe for each container should be different, so you could see which is failing.</p>
<p>Also use</p>
<pre><code>kubectl get pod &lt;pod&gt; -o yaml
</code></pre>
<p>and search for <code>containerStatuses</code>. There you can see the status of each container.</p>
