<p>We have a Gitlab CI/CD to deploy pod via Kubernetes. However, the updated pod is always pending and the deleted pod is always stuck at terminating.
<a href="https://i.stack.imgur.com/qmlKn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qmlKn.png" alt="enter image description here" /></a></p>
<p>The controller and scheduler are both okay.
<a href="https://i.stack.imgur.com/g0Y5j.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/g0Y5j.png" alt="enter image description here" /></a></p>
<p>If I described the pending pod, it shows it is scheduled but nothing else.
<a href="https://i.stack.imgur.com/iNGJq.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/iNGJq.png" alt="enter image description here" /></a></p>
<p>This is the pending pod's logs:</p>
<blockquote>
<p>$ kubectl logs -f robo-apis-dev-7b79ccf74b-nr9q2 -n xxx -f Error from
server (BadRequest): container &quot;robo-apis-dev&quot; in pod
&quot;robo-apis-dev-7b79ccf74b-nr9q2&quot; is waiting to start:
ContainerCreating</p>
</blockquote>
<p>What could be the issue? Our Kubernetes cluster never had this issue before.</p>

angelokh
<p>Okay, it turns out we used to have an NFS server as PVC. But we have moved to AWS EKS recently, thus cleaning the NFS servers. Maybe there are some resources from nodes that are still on the NFS server. Once we temporarily roll back the NFS server, the pods start to move to RUNNING state.</p>
<p>The issue was discussed here - Orphaned pod <a href="https://github.com/kubernetes/kubernetes/issues/60987" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/60987</a></p>
