mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-18 04:54:54 +00:00
The daemonset controller already has handling for NotFound errors. Right now if the statefulset controller is attempting to scale down a statefulset and its informer cache is stale, it can get hard-blocked on a missing pod. This issue will eventually self-resolve once the informer cache "catches up", but in the process of exploring this issue I realized that 404s during pod deletions don't strictly need to abort the entire sync; we can continue. This is especially impactful for large statefulsets with podManagementStrategy: Parallel, where a single "phantom" pod (actually missing, but still present in the informer cache) can block thousands of other pods from being cleaned up.