Menu

1 / 5

Pods stuck Pending after node failure: why didn't Kubernetes reschedule them to the other node?

DEV Community: kubernetes·KYUNGHWAN KIM·3 days ago
#iVFLeDoL
#devtokubernetes#devto#dev#node#pods
Reading 0:00
15s threshold

If your pods are not rescheduled when a node goes down and stay stuck Pending after node failure, run kubectl describe pod and read the FailedScheduling event. After a drain it reads 0/2 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) were unschedulable. ; after a node dies, the second item is 1 node(s) had untolerated taint {node.kubernetes.io/unreachable: } instead ( 1 node(s) had untolerated taint(s) on Kubernetes 1.35 and later). Either way, the pod has been recreated, and no node satisfies its own placement rules. On our cluster 15 stateless app Deployments carried a required node affinity, role NotIn [observability] , and the role=observability label is on the only other node, so each of them could run on exactly one node.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.