-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRA: Prioritized Alternatives in Device Requests #4816
Comments
/sig node |
@kannon92: The label(s) In response to this:
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. |
/milestone v1.32 |
/retitle DRA: Prioritized List of Devices just slightly shorter |
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 |
actually, one more time: /retitle DRA: Prioritized Alternatives in Device Requests |
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 Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
@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. |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
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! |
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 |
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). Thanks James Spurin |
@spurin placeholder is kubernetes/website#48516 Not sure this will make the release, but hopefully. |
👋 Hi there, William here from v1.32 Comms To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
Hello @johnbelamaric @klueska, Enhancements team here (again 😁 ) Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024. I was not able to find the PRs (code changes) related to this enhancements. All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests. I will mark this enhancement as at risk for code freeze for the v1.32 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. |
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:
Discussion Link:
Primary contact (assignee):
@klueska, @pohly, @johnbelamaric, @thockin
Responsible SIGs:
/sig node
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):The text was updated successfully, but these errors were encountered: