KEP: Surge capacity on eviction instead of blocking on PodDisruptionBudget - #6245
KEP: Surge capacity on eviction instead of blocking on PodDisruptionBudget#6245monta-riahi wants to merge 1 commit into
Conversation
Provisional KEP proposing an opt-in behavior where an exhausted PodDisruptionBudget triggers a surge of replacement capacity before an eviction completes, instead of blocking the eviction outright. Signed-off-by: Montassar Riahi <montassar.riahi@cimpress.com>
|
Welcome @monta-riahi! |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: monta-riahi The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @monta-riahi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Description from kubernetes/kubernetes #140599,
|
What this PR does
Adds a provisional KEP proposing an opt-in behavior where an exhausted PodDisruptionBudget triggers a surge of replacement capacity before an eviction completes, instead of blocking the eviction outright with
429 TooManyRequests.Today API-initiated eviction is a binary decision against the PDB: if
DisruptionsAllowed == 0the eviction is rejected indefinitely. For a single-replica Deployment withminAvailable: 1this makes the workload undrainable without an outage. This KEP proposes bringing up a replacement first (likemaxSurgein a rolling update) and releasing the eviction once the replacement is Ready.The document is intentionally
provisional: it frames the problem, lays out the three cooperating pieces (signal → surge → release), and enumerates the open design questions for SIG discussion (where surge intent lives, who owns the surge, non-surgeable workloads, and the async eviction contract). It is expected to compose with KEP-4212 Declarative Node Maintenance./sig node
/sig apps
/kind kep