KEP-3973keps/sig-apps/3973-consider-terminating-pods-deployment
Consider Terminating Pods in Deployments
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 new fi… 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 new fields status.terminatingReplicas to both Deployments and ReplicaSets in order to improve managed pod observability to eventually improve these scenarios in future efforts (KEP-5882).
Facts
- Authors
- @atiratree
- Approvers
- @soltysh
- Reviewers
- @kannon92@soltysh@jpbetz@knelasevero
- Tracking issue
- #3973(opens GitHub in a new tab) closednot_plannedclosed 2026-07-04 17:43 UTCsig/appsstage/betalifecycle/rotten
- Milestones
- alpha v1.33beta v1.35
- Participating SIGs
- none
- Feature gates
- DeploymentReplicaSetTerminatingReplicas
- Created / last updated
- 2023-12-12 / none
Loading decisions and status history