DRA: structured parameters #4381
Comments
k8s-ci-robot
added
the
needs-sig
|
/sig node The rationale behind creating a separate KEP is that this is an extension of DRA that (at least in theory) could graduate at its own pace. The KEP document itself also will be shorter, which will make discussing it easier. |
k8s-ci-robot
added
sig/node
|
/stage alpha |
k8s-ci-robot
added
the
stage/alpha
|
/milestone v1.30 |
|
@klueska: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility. 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/test-infra repository. |
|
@SergeyKanzhelev can we get this added to the 1.30 milestone? |
|
/label lead-opted-in |
k8s-ci-robot
added
the
lead-opted-in
|
@klueska: 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:
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/test-infra repository. |
|
/label lead-opted-in |
|
Hello @pohly 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just want to update the following but it's not required for
The status of this enhancement is marked as |
|
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
|
Hello @pohly 👋, 1.30 Docs Lead here. Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. |
|
Hi @pohly 👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
|
Doc PR for 1.30 created and linked to in the description. |
|
Hey again @pohly 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, I couldn't find any (open) PRs in k/k. With this, it is now marked as Please let me know if there are other PRs in k/k we should be tracking for this KEP. |
|
Hello @pohly 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting stage Here's where this enhancement currently stands:
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
|
Hello @pohly 👋, 1.31 Docs Shadow here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you! |
|
@prianna: I was a bit late with updating the issue description. What you looked at was the KEP update for 1.30, not the one for 1.31. However, the one for 1.31 also got reviewed, approved and merged before the deadline, so the end result is the same. Sorry for the confusion! @hacktivist123: I created a placeholder PR. |
|
Thanks for the update @pohly |
|
Hi @pohly, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
sreeram-venkitesh
added
the
tracked/yes
|
Hey @pohly, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
|
Hey again @pohly 👋 Enhancements team here, To avoid repeating myself too much (see #3063), I'll just note the below here as well. Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze: If you anticipate missing code freeze, you can file an exception request in advance. |
|
@hacktivist123 Same question here re: the transition to tracked? It doesn't look like this one is ready either. |
|
@pohly Is merging kubernetes/kubernetes#125488 related to this KEP? I could only find another PR, kubernetes/kubernetes#120611 related to this KEP. Please let us know if we should be tracking any other PRs as well. Ref: #3063 (comment) |
|
Yes, kubernetes/kubernetes#125488 is also for this KEP and got merged, so we are good for 1.31. |
|
Awesome, thanks a lot. Are we good to mark this KEP as tracked for code freeze? I'm also curious to know where kubernetes/kubernetes#120611 comes into picture. |
|
kubernetes/kubernetes#120611 is an optional PR for this feature in 1.31. Would be nice to have, but not required. |
|
Thanks a lot @pohly! Marking this KEP as |
|
The goal is to promote this to beta in 1.32, if possible. |
|
Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32. /remove-label lead-opted-in |
k8s-ci-robot
removed
the
lead-opted-in
|
/milestone v1.32 |
k8s-ci-robot
added
the
lead-opted-in
Much of the PRR text that was originally written for "classic DRA" applies also to "structured parameters". It gets moved from kubernetes#3063 to kubernetes#4381, with some minor adaptions. The placeholder comments get restored in kubernetes#3063 because further work on the KEP would be needed to move it forward - if it gets moved forward at all instead of being abandoned. The v1beta1 API will be almost identical to the v1alpha3 API, with just some minor tweaks to fix oversights. The kubelet gRPC gets bumped with no changes. Nonetheless, drivers should get updated, which can be done by updating the Go dependencies and optionally changing the API import.
Much of the PRR text that was originally written for "classic DRA" applies also to "structured parameters". It gets moved from kubernetes#3063 to kubernetes#4381, with some minor adaptions. The placeholder comments get restored in kubernetes#3063 because further work on the KEP would be needed to move it forward - if it gets moved forward at all instead of being abandoned. The v1beta1 API will be almost identical to the v1alpha3 API, with just some minor tweaks to fix oversights. The kubelet gRPC gets bumped with no changes. Nonetheless, drivers should get updated, which can be done by updating the Go dependencies and optionally changing the API import.
|
Hello @haircommander 👋, 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 beta for v1.32 (correct me, if otherwise). 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 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! |
Enhancement Description
One-line enhancement description (can be used as a release note): The original dynamic resource allocation (DRA) uses claim and class parameters that are opaque to Kubernetes. With structured parameters, kube-scheduler and Cluster Autoscaler can handle respectively simulate claim allocation themselves without relying on a third-party driver.
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4381-dra-structured-parameters/
Discussion Link: Batch WG meeting 20231207, DRA intro and plan in that meeting
Primary contact (assignee): @pohly
Responsible SIGs: SIG Node
Enhancement target (which target equals to which milestone):
Alpha in 1.30
k/enhancements) update PR(s): KEP 4381: add structured parameters for dynamic resource allocation #4384k/k) update PR(s): DRA: structured parameters kubernetes#123516k/website) update PR(s): DRA in Kubernetes 1.30: adds structured parameters website#45287Alpha in 1.31
k/enhancements) update PR(s): KEP-4381: DRA update for 1.31 #4709k/k) update PR(s): DRA for 1.31 kubernetes#125488k/website) update PR(s): DRA documentation for 1.31 website#46816Beta in 1.32
k/enhancements) update PR(s): KEP-4381: DRA: PRR and API for beta of structured parameters in 1.32 #4869k/k) update PR(s):k/website) update(s):The text was updated successfully, but these errors were encountered: