DRA: Node Reservations via ResourceClaims

[dom4ha]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Node Reservations via DRA ResourceClaims

• Kubernetes Enhancement Proposal: KEP-5147: DRA Node Reservations via ResourceClaims #5149

• Discussion Link: [Public] Node Reservation via DRA ResourceSlices

• Primary contact (assignee): @dom4ha

• Responsible SIGs: SIG Scheduling

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s): KEP-5147: DRA Node Reservations via ResourceClaims #5149
  • 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.

/sig scheduling
/assign

[alculquicondor]

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

[soltysh]

Based on this comment it seems this is being removed from 1.33 work.

[alculquicondor]

@dom4ha can we close this?

[dipesh-rawat]

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

I see that this KEP has been opted-out of v1.33 based on the comment #5149 (comment) and is now planned for a future release. I will go ahead and mark it as Deferred on the 1.33 release board for tracking purposes - do let the enhancement team know otherwise.

/milestone clear

[dom4ha]

Closing as the proposal got withdrawn. See KEP PR for a justification.

[Udi-Hofesh]

Hey @dom4ha 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!

For the 1.33 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 that fall into (but are 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 Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timelines to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 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.