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: https://github.com/kubernetes/enhancements/pull/5287
• Discussion Link: https://github.com/kubernetes/kubernetes/issues/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):
  • Beta release target (x.y): v1.34
  • Stable release target (x.y):

(Skipping alpha)

• [ ] Beta
  • [ ] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5287
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update(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

[fykaa]

Hi @sanposhiho @wojtek-t :wave:, v1.34 Enhancements team here.

This is a reminder of the upcoming PRR Freeze on Thursday 12th June 2025.

By this date, there must be a PR open in k/enhancements with:

• The KEP's PRR questionnaire filled out.
• The kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• A PRR approval file with the PRR approver listed for the stage the KEP is targeting.

Having the PRR questionnaire filled out by this deadline will help ensure that the PRR team has enough time to review your KEP before Enhancements Freeze on Friday 20th June 2025. For more information on the PRR process, see here.

[fykaa]

Hello @wojtek-t @sanposhiho 👋, v1.34 Enhancements team here again.

Just checking in as we approach Enhancements Freeze on 21:00 UTC Friday 20th June 2025.

This enhancement is targeting stage beta for v1.34 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable for latest-milestone: v1.34.
• [x] KEP readme has up-to-date graduation criteria
• [x] 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 { PRR_FREEZE_DATETIME } so that the PRR team has enough time to review your KEP.

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

• KEP merged to k/enhancements repo
• PRR completed and merged

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!

[wojtek-t]

@fykaa - the KEP just merged: https://github.com/kubernetes/enhancements/pull/5287 - I believe all the boxes should now be addressed.

[fykaa]

This looks great to me @wojtek-t! I'll update the status, thanks!

[graz-dev]

Hi @sanposhiho @wojtek-t 👋 -- this is Graziano (@graz-dev) from the 1.34 Communications Team!

For the 1.34 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday 11th July? For more information about writing a blog, please find the blog contribution guidelines 📚

[!Tip] Some timeline to keep in mind:

• 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
• Friday 8th August 2025: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[rashansmith]

Hello @sanposhiho @wojtek-t 👋, 1.34 Docs Shadow here!

Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[rashansmith]

Hello @sanposhiho @wojtek-t 👋, 1.34 Docs Shadow here!

Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Just a reminder to open a placeholder PR against dev-1.34 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs:

The deadline for this is Thursday July 3 at 18:00 PDT. Thanks! 🚀

[fykaa]

Hey again @sanposhiho @wojtek-t 👋, v1.34 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 25th July 2025 .

Here's where this enhancement currently stands:

• [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• https://github.com/kubernetes/kubernetes/pull/132443

If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visiblity. Alternativelty, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.

The status of this enhancement is marked as At risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

[graz-dev]

Hi @sanposhiho @wojtek-t 👋, 1.34 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Friday 11th July 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

[!Tip] Some timeline to keep in mind:

• 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
• Friday 8th August 2025: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[sanposhiho]

Sorry for the late update, I was on vacation for a while (and @/wojtek-t is on vacation too). I just created: https://github.com/kubernetes/website/pull/51523

[rashansmith]

Hello @sanposhiho @wojtek-t :wave: please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday July 29th 2025 18:00 PST. Thank you!

[jmickey]

Hello @sanposhiho @wojtek-t 👋, v1.34 Enhancements team here,

Unfortunately, the implementation (code-related) PRs associated with this enhancement are not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.34 milestone.

Additionally, if any of the merged implementation PRs for this enhancement include user-facing changes, please let us know. This will help us determine whether the changes should be documented or considered for rollback to maintain release integrity.

If you still wish to progress this enhancement in v1.34, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/label tracked/no /milestone clear

[sanposhiho]

I filed the exception

[jenshu]

Hi @sanposhiho @wojtek-t,

As far as I can tell, here is the current status for 1.34 code freeze, please correct me if wrong:

These PRs are merged, and there are no further k/k code PRs required for code freeze:

• https://github.com/kubernetes/kubernetes/pull/133276
• https://github.com/kubernetes/kubernetes/pull/132443
• https://github.com/kubernetes/kubernetes/pull/133021
• https://github.com/kubernetes/kubernetes/pull/133213
• https://github.com/kubernetes/kubernetes/pull/133293 (alpha downgrade)

Will not be included in 1.34:

• https://github.com/kubernetes/kubernetes/pull/133215

Before we mark this as tracked for code freeze, can you please update the docs (in k/website) and KEP files (in k/enhancements) to reflect that this KEP is now targeting alpha (instead of beta) in 1.34? Once those PRs are open/approved, we can move this to tracked for code freeze. Thanks!

[sanposhiho]

@jenshu Yes, your understanding is right. I also updated the doc pr.

[jenshu]

As the KEP alpha update has merged, I'm updating this to Tracked for code freeze

/remove-label tracked/no /label tracked/yes /milestone v1.34

[rayandas]

Hi @sanposhiho :wave:, v1.35 Enhancements Lead here.

I am closing the v1.34 milestone now.

If you'd like to work on this enhancement in v1.35, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.35 using /milestone v1.35.

Thanks!

/remove-label lead-opted-in /remove-label tracked/yes /milestone clear

[macsko]

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

[kannon92]

Will this be alpha for 1.35?

[sanposhiho]

It's already alpha in the last release, and will be beta in 1.35.

[sanposhiho]

/assign @ania-borowiec

[sanposhiho]

We discussed internally and decided not to prioritize it this release. Especially because we're not 100% sure about how NNN would fit after the reservation-ish thing comes.