---
title: "Discussion on \"Pods stuck Pending after node failure: why didn't Kubernetes reschedule them to the other node?\" | Hashnode"
description: "Discussion on \"Pods stuck Pending after node failure: why didn't Kubernetes reschedule them to the other node?\". Pods stuck Pending after node failure: a required NotIn node affinity and two topology spread defaults on a 2-node k3s cluster. How to check yours."
url: "https://hashnode.com/posts/pods-stuck-pending-after-node-failure-why-didn-t-kubernetes-reschedule-them-to-the-other-node/6af68e354617070ad9bb638a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Pods stuck Pending after node failure: why didn't Kubernetes reschedule them to the other node?](https://kkhdevs.hashnode.dev/pods-stuck-pending-after-node-failure-why-didn-t-kubernetes-reschedule-them-to-the-other-node?utm_source=hashnode&utm_medium=feed)

Pods stuck Pending after node failure: a required NotIn node affinity and two topology spread defaults on a 2-node k3s cluster. How to check yours.

7h ago · 24 min read · kkhdevs.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#scheduling](https://hashnode.com/tag/scheduling)
-   [#sre](https://hashnode.com/tag/sre)
-   [#devops](https://hashnode.com/tag/devops)
-   [#postmortem](https://hashnode.com/tag/postmortem)

## Written by

[KIM KYUNGHWAN](https://hashnode.com/@kkhdevs)

@kkhdevs

  
[View profile](https://hashnode.com/@kkhdevs)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.