# Pod stuck after restarting a node

**URL:** <https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231>\
**Category:** General Discussions\
**Tags:** network\
**Created:** [September 16, 2026, 3:43pm UTC](https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231 "2026-09-16T15:43:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![islabrown190](https://avatars.discourse-cdn.com/v4/letter/i/a88e57/32.png) [@islabrown190](https://discuss.kubernetes.io/u/islabrown190)\
**Post date:** [September 16, 2026, 3:43pm UTC](https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231/1 "2026-09-16T15:43:28Z")

</div>

Hi, I’m testing a small kubertenes cluster and noticed that after restarting one of the nodes[,](https://geometrrydashapk.com/) one of my pods sometimes stays in pending for a while. what’s the first thing you actually check in this situation? kubectl describe pod shows that it is waiting for a suitable node, but I’m not sure which part I should investigate first.

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://discuss.kubernetes.io/u/discourse_ai_spam)\
**Post date:** [September 16, 2026, 3:43pm UTC](https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231/2 "2026-09-16T15:43:29Z")

</div>

Unlisted on September 16, 2026, 3:43pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/1X/786dc982abab8f78c3762424fae045d4b084cf3d.png) [@system](https://discuss.kubernetes.io/u/system)\
**Post date:** [September 21, 2026, 8:09am UTC](https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231/3 "2026-09-21T08:09:01Z")

</div>

Listed on September 21, 2026, 8:09am UTC



---

<div class="post-metadata">

**Author:** ![Team\_Adminguide](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/team_adminguide/32/18651_2.png) [@Team\_Adminguide](https://discuss.kubernetes.io/u/Team_Adminguide)\
**Post date:** [November 6, 2026, 12:37pm UTC](https://discuss.kubernetes.io/t/pod-stuck-after-restarting-a-node/35231/4 "2026-11-06T12:37:12Z")

</div>

First, check why the Pod is stuck:

```auto
kubectl describe pod <pod-name> -n <namespace>
kubectl get nodes -o wide
kubectl uncordon <node-name>

```

Check the scheduling errors, node status, resources, and taints. If the node is marked SchedulingDisabled, check whether it was intentionally cordoned. If it is safe to accept new Pods, run kubectl uncordon. Also check whether the Pod has been assigned to a node; if so, investigate image pulling, storage, and container startup before deleting it.

References: [Kubernetes Pod Troubleshooting](https://kubernetes.io/docs/tasks/debug/debug-application/debug-pods/) · [Node Status](https://kubernetes.io/docs/reference/node/node-status/) · [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) · [Node Troubleshooting](https://kubernetes.io/docs/tasks/debug/debug-cluster/)
