KEP-5882keps/sig-apps/5882-deployment-pod-replacement-policy
Deployment Pod Replacement Policy
Deployments have inconsistent behavior in how they handle terminating pods, depending on the rollout strategy and when scaling the Deployments. In some scenarios it may be advantageous to wait for terminating pods to terminate before spinning new ones. In other scenarios it might be beneficial to spin them as soon as possible. This KEP proposes to add a new… Full summary
Deployments have inconsistent behavior in how they handle terminating pods, depending on the rollout strategy and when scaling the Deployments. In some scenarios it may be advantageous to wait for terminating pods to terminate before spinning new ones. In other scenarios it might be beneficial to spin them as soon as possible. This KEP proposes to add a new field .spec.podReplacementPolicy to Deployments to allow users to specify the desired behavior. This KEP builds on top of the KEP-3973 that helped to introduce status.terminatingReplicas fields to Deployments and ReplicaSets.
Facts
- Authors
- @atiratree
- Approvers
- @soltysh
- Reviewers
- @kannon92@soltysh@jpbetz@knelasevero
- PRR approvers
- @wojtek-talpha
- Tracking issue
- #5882(opens GitHub in a new tab) opensig/appsstage/alpha
- Milestones
- alpha v1.36
- Participating SIGs
- none
- Feature gates
- DeploymentPodReplacementPolicy
- Created / last updated
- 2026-02-03 / none
Loading decisions and status history