<p>Curiously, I saw that a pod I had had both ready 1/1 status and status <code>terminating</code> when I ran <code>kubectl get pods</code>. Are these states not mutually exclusive? Why or why not?</p>

<p>For context, this was noticed immediately after I had killed <code>skaffold</code> so these pods were in the middle of shutting down. </p>

<p><a href="https://i.stack.imgur.com/mY5S8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mY5S8.png" alt="enter image description here"></a></p>

<p>When pods are in terminating state, they could still be functioning. The pod could be delayed in termination due to many reasons (eg. could be that you have a PVC attached, other pods are being terminated at the same time, etc). You could test this by running the following on a pod with a PVC attached or another reason to be terminated with a delay:</p>

<pre><code>$ kubectl delete pod mypod-xxxxx-xxxxxx
pod mypod-xxxxx-xxxxxx deleted

$ kubectl delete pod mypod-xxxxx-xxxxxx
pod mypod-xxxxx-xxxxxx deleted

$ kubectl apply mypod.yaml
pod mypod-xxxxx-xxxxxx configured
</code></pre>

<p>Sometimes this happens because the pod is still in the terminating period and is functioning normally, so it will be treated as an existing pod that gets configured (neglecting the fact that you usually can't configure pods like this, but you get the point).</p>
