# A node died, brought back up, but none of the pods rescheduled on it

**URL:** <https://discuss.kubernetes.io/t/a-node-died-brought-back-up-but-none-of-the-pods-rescheduled-on-it/10475>\
**Category:** General Discussions\
**Created:** [April 10, 2020, 11:56pm UTC](https://discuss.kubernetes.io/t/a-node-died-brought-back-up-but-none-of-the-pods-rescheduled-on-it/10475 "2020-04-10T23:56:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nodesocket](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/nodesocket/32/4369_2.png) [@nodesocket](https://discuss.kubernetes.io/u/nodesocket)\
**Post date:** [April 10, 2020, 11:56pm UTC](https://discuss.kubernetes.io/t/a-node-died-brought-back-up-but-none-of-the-pods-rescheduled-on-it/10475/1 "2020-04-10T23:56:16Z")

</div>

Running a 3 node cluster on AWS EKS 1.13.7. One of the backing ec2 instances had some sort of issue, so I stopped it, and the AWS auto-scaling group kicked in and created a new ec2 instance. All good, except now none of my pods are running on the new ec2 instance. All the pods are running on the two other nodes. How can I have Kubernetes reschedule pods evenly again across all nodes? This seems like something Kubernetes should handel.

---

<div class="post-metadata">

**Author:** ![michaelpporter](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/michaelpporter/32/4939_2.png) [@michaelpporter](https://discuss.kubernetes.io/u/michaelpporter)\
**Post date:** [April 11, 2020, 10:57am UTC](https://discuss.kubernetes.io/t/a-node-died-brought-back-up-but-none-of-the-pods-rescheduled-on-it/10475/2 "2020-04-11T10:57:57Z")

</div>

It is my experience that they will not reschedule on their own. Here is an article I read the explains scheduling [https://itnext.io/keep-you-kubernetes-cluster-balanced-the-secret-to-high-availability-17edf60d9cb7](https://itnext.io/keep-you-kubernetes-cluster-balanced-the-secret-to-high-availability-17edf60d9cb7)