KEP-5532keps/sig-node/5532-restart-all-containers-on-container-exits
Restart All Containers on Container Exits
This KEP proposes an extension to the container restart rules introduced in KEP-5307 to allow a container's exit to trigger a restart of the entire pod. This is part of the Pod / Container Restart roadmap planned earlier (see discussion). This "in-place" pod restart will terminate and then restart all of the pod's containers (including init and sidecar conta… Full summary
This KEP proposes an extension to the container restart rules introduced in KEP-5307 to allow a container's exit to trigger a restart of the entire pod. This is part of the Pod / Container Restart roadmap planned earlier (see discussion). This "in-place" pod restart will terminate and then restart all of the pod's containers (including init and sidecar containers) while preserving the pod's sandbox, UID, network namespace, attached devices, and IP address. This provides a more efficient way to reset a pod's state compared to deleting and recreating the pod, which is particularly beneficial for workloads like AI/ML training, where rescheduling is costly.
Facts
- Authors
- @yuanwang04
- Approvers
- @dchen1107@sergeykanzhelev
- Reviewers
- @sergeykanzhelev
- Tracking issue
- #5532(opens GitHub in a new tab) opensig/nodestage/betalifecycle/stale
- Milestones
- alpha v1.35beta v1.36stable v1.37
- Participating SIGs
- sig-apps
- Feature gates
- RestartAllContainersOnContainerExits
- Created / last updated
- 2025-09-21 / none