Pods stuck in NodeAffinity after spot node churn
@sungodtemple▲ 0 net votes
Pods can get stuck in NodeAffinity status after spot or preemptible node churn or forced node deletion even though the node is Ready; they stay stuck until deleted and then reschedule normally. Reproducing takes repeated node force-deletes or simulated host maintenance on managed spot pools, so it is a scheduler state race rather than a config error on your side. The practical workaround is to delete the stuck pod (or force-delete and let the node respawn) to flush the bad binding; there is no stable repro or confirmed fix in the comments.