DRA: Prioritized Alternatives in Device Requests

[klueska]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add support for a "one-of" prioritized list of selection criteria to satisfy a device request in a resource claim.

• Kubernetes Enhancement Proposal:

  • https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4816-dra-prioritized-list/README.md

• Discussion Link:

  • https://github.com/kubernetes-sigs/wg-device-management/blob/0ec4f1ca783e550933de01533b7fb7b7ab14defb/dra-evolution/pkg/api/claim_types.go#L201-L208

• Primary contact (assignee):
  @klueska, @pohly, @johnbelamaric, @thockin

• Responsible SIGs:
  /sig scheduling
  /sig node

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

  • Alpha release target: 1.33
  • Beta release target: 1.34
  • Stable release target: 1.35

• Alpha

  • KEP (k/enhancements) update PR(s):
    • KEP-4816: DRA Prioritized Alternatives in Device Requests #4871
    • KEP-4816 DRA Prioritized List design update #5065
  • Code (k/k) update PR(s):
    • Prioritized Alternatives in Device Requests kubernetes#128586
  • Docs (k/website) update PR(s):
    • KEP-4816 DRA Prioritized List website#48516

[kannon92]

/sig node
/wg device-management

[k8s-ci-robot]

@kannon92: The label(s) wg/device-management cannot be applied, because the repository doesn't have them.

In response to this:

/sig node
/wg device-management

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.

[haircommander]

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

[johnbelamaric]

/retitle DRA: Prioritized List of Devices

just slightly shorter

[pohly]

It's not listing "devices"? How about "DRA: alternatives in device requests"?

[johnbelamaric]

It's not listing "devices"? How about "DRA: alternatives in device requests"?

Yes, sure, except I want the "prioritized" part in there.

/retitle DRA: Prioritized List of Device Requests

[johnbelamaric]

actually, one more time:

/retitle DRA: Prioritized Alternatives in Device Requests

[shecodesmagic]

Hello @klueska @johnbelamaric 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• KEP readme has up-to-date graduation criteria
• 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 Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• KEP readme has up-to-date graduation criteria

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[johnbelamaric]

@shecodesmagic I unchecked the PRR box - I am a PRR approver but shouldn't approve my own KEP. I haven't done the PRR section yet. I assigned @jpbetz to do the PRR for me.

[shecodesmagic]

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[chanieljdan]

Hi @johnbelamaric 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 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!

[spurin]

Hi @johnbelamaric 👋,

Just a reminder to open a placeholder PR against dev-1.32 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 Oct 24 at 18:00 PDT.

Thanks

James Spurin

[spurin]

Hi @johnbelamaric,

Hope all is well. Quick followup to remind you we'll need at least a placeholder PR for documentation against the dev-1.32 branch. The deadline is tomorrow (Thursday Oct 24 at 18:00 PDT).

cc: @chanieljdan @katcosgrove

Thanks

James Spurin

[jpbetz]

PRR reviewer here. Is there a KEP update PR available for review for this enhancement? Deadline is TOMORROW.

[kannon92]

PRR reviewer here. Is there a KEP update PR available for review for this enhancement? Deadline is TOMORROW.

I think the KEP went in for 1.32 already. The implementation slipped to 1.33.

@johnbelamaric Will there will be a KEP update for this feature?

[johnbelamaric]

PRR from 1.32 is still valid, nothing changed that is production readiness related.

[johnbelamaric]

I believe this is all completed in #5065

@bianbbc87 please confirm.

[bianbbc87]

@johnbelamaric

Hello ! I checked changed.

Please add #5065 under alpha kep of this pr and change it to alpha release target: 1.33.

Thank you !

[johnbelamaric]

Please add #5065 under alpha kep of this pr and change it to alpha release target: 1.33.

done

[sreeram-venkitesh]

Hi @johnbelamaric! 👋 v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 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!

[mortent]

Docs placeholder PR: kubernetes/website#49869

[mortent]

/assign

[rytswd]

Hi @klueska @pohly @johnbelamaric @thockin 👋 -- this is Ryota (@rytswd) 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 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 Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline 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.

[sn3hay]

Hi @klueska , @pohly, @johnbelamaric and @thockin 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 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 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.

[mortent]

@sn3hay I have created a placeholder PR for a feature blog about this feature: kubernetes/website#49993. We might want to make a single blog covering both prioritized list and partitionable devices, but I've created separate placeholder PRs for now.

@johnbelamaric Could you add links to both the docs and blog placeholder PRs in the issue description (I don't have permissions to edit it):

• Docs PR: Document DRA prioritized list(s) website#49869
• Blog PR: Blog with DRA updates in 1.33 website#49993

[bianbbc87]

Hey again @klueska 👋, v1.33 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 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):

• Prioritized Alternatives in Device Requests kubernetes#128586

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.

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

As always, we are here to help if any questions come up. Thanks!

[dipesh-rawat]

@klueska @mortent @pohly Now that all the implementation(code related) PRs merged as per the issue description:

• Prioritized Alternatives in Device Requests kubernetes#128586

This enhancement is now marked as tracked for code freeze for the v1.33 Code Freeze!

Also, please let us know if anything changes before the freeze or if there are any other PRs in k/k we should track for this KEP to keep the status accurate.

[lauralorenz]

4/29 WG-device-management note: Must decide what we are doing for this cycle (go to beta? address questions on the grad criteria?)