Use NominatedNodeName to express the expected pod placement

[sanposhiho]

Enhancement Description

• One-line enhancement description (can be used as a release note): Use NominatedNodeName to express the expected pod placement
• Kubernetes Enhancement Proposal: kep-5278: nominated node name for an expected pod placement #5287
• Discussion Link: Scheduler pre-binding can cause race conditions with automated empty node removal kubernetes#125491, SIG-Scheduling meeting on May 6th
• Primary contact (assignee): @sanposhiho @wojtek-t
• Responsible SIGs: SIG-Scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.34
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • 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.

[sanposhiho]

/sig scheduling

[sanposhiho]

/assign @sanposhiho @wojtek-t
/cc @kubernetes/sig-scheduling-leads

[sanposhiho]

/sig autoscaling

participating sig.

[sanposhiho]

/cc @mimowo @tenzen-y
Kueue might want to use this for a soft scheduling requirement. (I will clarify what we mean on KEP)

[tenzen-y]

/cc @mimowo @tenzen-y Kueue might want to use this for a soft scheduling requirement. (I will clarify what we mean on KEP)

Thank you for letting us know. Let me know once you open KEP.

[sanposhiho]

/label lead-opted-in
We agreed we're going to put the effort in this in this release cycle

[sanposhiho]

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

[sanposhiho]

I'm not sure why lead-opted-in didn't work 🤔 Adding directly