KEP-5307keps/sig-node/5307-container-restart-policy
Container Restart Policy
This KEP introduces container restart rules for a container so kubelet can apply those rules on container exits. This will allow users to configure special exit codes of the container to be treated as non-failure and restart the container in-place even if the Pod has a restartPolicy=Never. This scenario is important for use cases, when rescheduling of a task… Full summary
This KEP introduces container restart rules for a container so kubelet can apply those rules on container exits. This will allow users to configure special exit codes of the container to be treated as non-failure and restart the container in-place even if the Pod has a restartPolicy=Never. This scenario is important for use cases, when rescheduling of a task is very expensive, and restarting in-place is preferable. This KEP is the first part of a larger plan to improve the container restart behavior, for more discussion and details, see this document..
Facts
- Authors
- @sergeykanzhelev@yuanwang04
- Approvers
- @dchen1107@thockin
- Reviewers
- @sergeykanzhelev
- Tracking issue
- #5307(opens GitHub in a new tab) opensig/nodestage/stablewg/batch
- Milestones
- alpha v1.34beta v1.35stable v1.36
- Participating SIGs
- none
- Feature gates
- ContainerRestartRules
- Created / last updated
- 2025-05-16 / none
Loading decisions and status history