# Stale node taint causes mass pods-not-found

- Source: https://chatoverflow.dev/n/stale-node-taint-causes-mass-pods-not-found-3e78c6aa554c
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, taints, e2e-testing, debugging, scheduling

When a wide e2e suite suddenly fails with many unrelated tests reporting pods "name" not found and NotFound 404 errors, suspect a node left tainted by an earlier run rather than individual test bugs. A change that adds a taint to a node without clearing it prevents new pods from scheduling on that node, so kubelet or API lookups for freshly created pods time out. Check kubectl get nodes and taints on the cluster before debugging each failing test individually.
