Beta requirement: QueueingHint

[sanposhiho]

/assign
/sig scheduling

This is an issue for tracking all requirements for QueueingHint to be Beta (= enabled by default).

• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4247-queueinghint/README.md

---

Tasks

Beta Give feedback

1. scheduler: move all preCheck to QueueingHint #110175
   kind/bug sig/scheduling triage/accepted +3
   
2. Implement the integration tests for requeueing scenarios #122305
   kind/feature needs-triage priority/important-soon sig/scheduling +4
   
3. scheduler: handle in-flight Pods with less memory #120622
   0 of 3
   kind/feature needs-triage sig/scheduling +3
   
4. [Umbrella] Implement QueueingHintFn in in-tree plugins #118893
   kind/feature priority/important-longterm sig/scheduling triage/accepted +4
   

   
5. When PreFilter's PreFilterResult filter out some Nodes, unschedulable plugin isn't registered for those plugins #122018
   kind/bug lifecycle/stale needs-triage sig/scheduling +4
   
6. Improve how to move Pods when Pods are updated #121183
   kind/feature needs-triage sig/scheduling +3
   
7. Scheduler: same Pod can exist in both scheduling cycle and scheduling queue #118226
   kind/bug needs-triage sig/scheduling +3
   
8. Assigned Pod add/update events don't requeue Pods without PodAffinity #122626
   kind/bug needs-triage sig/scheduling +3
   
9. Scheduler: Observe/Improve event handling throughput #124566
   kind/feature needs-triage sig/scheduling +3
   

[k8s-ci-robot]

@sanposhiho: The label(s) kind/enhancement cannot be applied, because the repository doesn't have them.

In response to this:

/assign
/kind enhancement
/sig scheduling

This is an issue for tracking all requirements for QueueingHint to be Beta (= enabled by default).

• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4247-queueinghint/README.md

---

- [ ] https://github.com/kubernetes/kubernetes/issues/110175
- [ ] https://github.com/kubernetes/kubernetes/issues/120622
- [ ] https://github.com/kubernetes/kubernetes/issues/118893
- [ ] https://github.com/kubernetes/kubernetes/issues/122018
- [ ] https://github.com/kubernetes/kubernetes/issues/121183
- [ ] https://github.com/kubernetes/kubernetes/pull/119607
- [ ] https://github.com/kubernetes/kubernetes/pull/120586

Instructions 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/test-infra repository.

[sanposhiho]

/kind feature

[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

[sanposhiho]

/remove-lifecycle stale
/triage accepted