Asynchronous API calls during scheduling

[macsko]

Enhancement Description

• One-line enhancement description (can be used as a release note): Make API calls during scheduling asynchronous.
• Kubernetes Enhancement Proposal:
• Discussion Link: https://github.com/kubernetes/kubernetes/issues/129449, https://github.com/kubernetes/kubernetes/issues/130668
• 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.34
  • Stable release target (x.y):
• [ ] Beta
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5249
  • [ ] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/issues/132452
  • [ ] 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.

[macsko]

/sig scheduling /assign

[sanposhiho]

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

[drewhagen]

Howdy @macsko 👋

A friendly reminder from the v1.34 Enhancements team: the PRR Freeze is approaching on Thursday, June 12th, 2025.

To help ensure enough time for a smooth review by the PRR team and keep us all on track for the Enhancements Freeze (Friday, June 20th, 2025), please ensure that by the June 12th deadline, you have a PR open in k/enhancements which includes:

• The KEP's PRR questionnaire filled out.
• The kep.yaml updated with the stage, latest-milestone, and milestone struct.
• A PRR approval file with the PRR approver listed for the KEP's target stage.
• Completing these items by the deadline is key for the v1.34 release progression. You can find more details on the process in the Production Readiness documentation.

Your efforts on this KEP are making a real impact! 🚀 Thanks for your great contributions, SIG Release v1.34 Enhancements Team

[sanposhiho]

(Oops sorry, looks like I made some mistake and closed this issue)

[drewhagen]

Hello @macsko 👋, 1.34 Enhancements team here.

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

This enhancement is targeting stage beta for 1.34 (correct me, if otherwise). I'm curious to ask, why is this going directly with beta without there being an alpha? Please let me know 🙂

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 submitted a production readiness review and a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update:

• Looks like PR is close to merging in, has a lgtm. If you can merge it in this week before the deadline, we'll be good to go!

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!

[drewhagen]

Hello @macsko 👋, 1.34 Enhancements team here.

With all the requirements fulfilled, I can confirm this enhancement is now marked as tracked for enhancements freeze 🚀

/label tracked/yes

[dipesh-rawat]

Hi @macsko 👋 -- this is Dipesh (@dipesh-rawat) from the v1.34 Communications Team!

For the v1.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.

[michellengnx]

Hello @macsko 👋, 1.34 Docs Lead 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!

[yujen77300]

Hello @macsko 👋, 1.34 Docs Lead 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!

Hi @macsko 👋, 1.34 Docs Shadow here.

Just a reminder to open a placeholder PR against the dev-1.34 branch in the k/website repo if this KEP needs new or updated docs. (steps available here) If this KEP doesn’t require any docs updates, please kindly confirm that here too.

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

[macsko]

@yujen77300 Thanks for a reminder. Created https://github.com/kubernetes/website/pull/51473

[dipesh-rawat]

Hi @macsko 👋, v1.34 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned previously (here), 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.

[drewhagen]

Hey again @macsko 👋, 1.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:

• [x] 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/issues/132452

(Which appears to be the umbrella for):

• https://github.com/kubernetes/kubernetes/issues/132486
• https://github.com/kubernetes/kubernetes/issues/132489
• https://github.com/kubernetes/kubernetes/issues/132490
• https://github.com/kubernetes/kubernetes/issues/132491
• https://github.com/kubernetes/kubernetes/issues/132492
• https://github.com/kubernetes/kubernetes/issues/132493
• https://github.com/kubernetes/kubernetes/issues/132494
• https://github.com/kubernetes/kubernetes/issues/132495
• https://github.com/kubernetes/kubernetes/issues/132496

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!

[drewhagen]

Hey again @macsko 👋, 1.34 Enhancements team here.

A friendly reminder for your planning next week, we're soon approaching code freeze at 02:00 UTC Friday 25th July 2025. Please see my post above.

Thanks, and have a great weekend! 😄

[yujen77300]

Hello @macsko 👋, 1.34 Docs Shadow here.  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!

[drewhagen]

Hey @macsko, I didn't see any of these PRs in the umbrella issue: https://github.com/kubernetes/kubernetes/pull/133120 https://github.com/kubernetes/kubernetes/pull/132886

We are approaching code freeze momentarily. Are these required for 1.34?

[drewhagen]

Hello @macsko 👋, 1.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 1.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 1.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

[macsko]

Hello @drewhagen

FYI, I filed an exception request for this feature.

[macsko]

Hi @drewhagen,

The exception was granted and the code for this enhancement is fully merged. The docs PR is still pending.

[jenshu]

As the 2 remaining PRs

• https://github.com/kubernetes/kubernetes/pull/132886
• https://github.com/kubernetes/kubernetes/pull/133120

have merged, this is now tracked for code freeze!

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

[rayandas]

Hi @macsko :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

[sanposhiho]

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

[sanposhiho]

Oops, sorry. I meant a different one. We don't have anything to do with it in this release.

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

[k8s-ci-robot]

@sanposhiho: Those labels are not set on the issue: lead-opted-in

In response to this:

Oops, sorry. I meant a different one. We don't have anything to do with it in this release.

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

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-sigs/prow repository.

[kannon92]

/remove-label lead-opted-in

[k8s-ci-robot]

@kannon92: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to this:

/remove-label lead-opted-in

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-sigs/prow repository.

[kannon92]

@sanposhiho can you try again to remove label?

[sanposhiho]

/remove-label lead-opted-in

[sanposhiho]

didn't work. So I manually removed it 😅