Pop pod from backoffQ when activeQ is empty

[macsko]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow to pop pod from backoffQ when activeQ is empty in scheduler
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/5142-pop-backoffq-when-activeq-empty/README.md
• Discussion Link: Pop from the backoff queue whenever the active queue is empty kubernetes#129806
• Primary contact (assignee): @macsko
• Responsible SIGs: SIG Scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): n/a
  • Beta release target (x.y): 1.33
  • Stable release target (x.y):
• Beta
  • KEP (k/enhancements) update PR(s): KEP-5142: Pop pod from backoffQ when activeQ is empty #5144
  • Code (k/k) update PR(s):
    • (preparation) Split backoffQ into backoffQ and errorBackoffQ in scheduler kubernetes#130214
    • Call PreEnqueue plugins before adding pod to backoffQ kubernetes#130492
    • Update backoffQ's less function to order pods by priority in windows kubernetes#130680
    • Pop from backoffQ when activeQ is empty kubernetes#130772
  • Docs (k/website) update PR(s): KEP-5142: Add SchedulerPopFromBackoffQ feature gate docs website#49840

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

/sig scheduling
/assign

[alculquicondor]

/label lead-opted-in
/milestone v1.33

[dipesh-rawat]

Hello @macsko 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage alpha for v1.33 (correct me, if otherwise)
/stage alpha

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.33.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would need to update the following:

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hi @macsko 👋, 1.33 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

The current status of this enhancement is marked as At risk for enhancement freeze. There are a few requirements mentioned in the comment #5142 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hello @macsko 👋, 1.33 Enhancements team here,

Now that PR #5144 has been merged, all the KEP requirements are in place and merged into k/enhancements.

Before the enhancement freeze, it would be appreciated if following nit could be addressed:

• Update issue description to add direct link to KEP README.md.

  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/5142-pop-backoffq-when-activeq-empty/README.md

Aside from the minor nit mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is now marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

/stage beta
/label tracked/yes