KEP-3017keps/sig-apps/3017-pod-healthy-policy-for-pdb
Pod Healthy Policy for PDB
Pod Disruption Budgets currently don't provide a way for users to specify how to handle pods that are Running, but not Healthy (Ready). In this KEP, we add a new field unhealthyPodEvictionPolicy that allows users to specify what should happen to these not Healthy (Ready) pods. Whether they should be always evicted or kept in case the application guarded by a… Full summary
Pod Disruption Budgets currently don't provide a way for users to specify how to handle pods that are Running, but not Healthy (Ready). In this KEP, we add a new field unhealthyPodEvictionPolicy that allows users to specify what should happen to these not Healthy (Ready) pods. Whether they should be always evicted or kept in case the application guarded by a Pod Disruption Budget is not available and disrupted.
Facts
- Tracking issue
- #3017(opens GitHub in a new tab) closedcompletedclosed 2024-09-07 03:14 UTCmilestone v1.31sig/appsstage/stable
- Milestones
- alpha v1.26beta v1.27stable v1.31
- Participating SIGs
- sig-schedulingsig-node
- Feature gates
- PodDisruptionBudgetPodHealthyPolicy
- Created / last updated
- 2021-10-24 / none