KEP-4781keps/sig-node/4781-kublet-restart-pod-status
Restarting kubelet does not change pod status
When a kubelet restarts, for whatever reason, it usually will not have any impact on currently running pods. Today, however, a kubelet restart causes all pods on that node to have their Started and Ready statuses set to False (by the kubelet), which can disrupt services that were actually functioning normally. This KEP proposes improving Pod readiness manage… Full summary
When a kubelet restarts, for whatever reason, it usually will not have any impact on currently running pods. Today, however, a kubelet restart causes all pods on that node to have their Started and Ready statuses set to False (by the kubelet), which can disrupt services that were actually functioning normally. This KEP proposes improving Pod readiness management in the kubelet to ensure that the status of Pods is not unilaterally modified, and is instead preserved during kubelet restarts.
Facts
- Authors
- @chenk008@hirazawaui
- Approvers
- @dchen1107
- Reviewers
- @sergeykanzhelev@thockin@tallclair
- PRR approvers
- none
- Tracking issue
- #4781(opens GitHub in a new tab) opensig/nodestage/alpha
- Milestones
- deprecated v1.35
- Participating SIGs
- sig-network
- Feature gates
- ChangeContainerStatusOnKubeletRestart
- Created / last updated
- 2025-08-23 / none
Loading decisions and status history