Guarantee PodDisruptionBudget When Preemption Happens

[AxeZhan]

Enhancement Description

• One-line enhancement description (can be used as a release note): Guarantee PodDisruptionBudget When Preemption Happens
• Kubernetes Enhancement Proposal: https://docs.google.com/document/d/1g2wj8S04M0yTy2t4l4GzrdARtxBpkBTfkJHw0oqBvXM/edit?usp=sharing
• Discussion Link: https://github.com/kubernetes/kubernetes/issues/91492#issuecomment-1029484252
• Primary contact (assignee): @AxeZhan
• Responsible SIGs: sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y): TBD
  • Stable release target (x.y): TBD
• [ ] Alpha
  • [ ] KEP (k/enhancements) update PR(s):
    • https://github.com/kubernetes/enhancements/pull/3755
    • https://github.com/kubernetes/enhancements/pull/4665
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

Notice that this KEP is not a whole new KEP. It only took over https://github.com/kubernetes/enhancements/issues/3280. This new issue is created for better tracking(I can't update the old issue😢)

[AxeZhan]

/sig scheduling

[atiratree]

Can you please also transfer all the links to this issue description from the original issue?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten