DRA: structured parameters

[pohly]

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 release target (x.y): 1.30
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha in 1.30
  • KEP (k/enhancements) update PR(s): KEP 4381: add structured parameters for dynamic resource allocation #4384
  • Code (k/k) update PR(s): DRA: structured parameters kubernetes#123516
  • Docs (k/website) update PR(s): DRA in Kubernetes 1.30: adds structured parameters website#45287
• Alpha in 1.31
  • KEP (k/enhancements) update PR(s): KEP-4381: DRA update for 1.31 #4709
  • Code (k/k) update PR(s): DRA for 1.31 kubernetes#125488
  • Docs (k/website) update PR(s): DRA documentation for 1.31 website#46816

[pohly]

/sig node
/wg batch

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.

[SergeyKanzhelev]

/stage alpha
/milestone v1.30

[klueska]

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

[k8s-ci-robot]

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

/milestone v1.30
/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/test-infra repository.

[johnbelamaric]

@SergeyKanzhelev can we get this added to the 1.30 milestone?

[johnbelamaric]

/label lead-opted-in

[k8s-ci-robot]

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

/milestone v1.30
/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/test-infra repository.

[SergeyKanzhelev]

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

[salehsedghpour]

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 alpha for v1.30 (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: 1.30.
• 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).

For this KEP, we would just want to update the following but it's not required for alpha stage and it will serve for future stages:

• Make sure that the KEP 4381: add structured parameters for dynamic resource allocation #4384 is merged to the k/enhancements repo.

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, I couldn't find any related PR regarding this KEP in k/enhancements. Thank you!

[salehsedghpour]

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

[drewhagen]

Hello @pohly 👋, 1.30 Docs Lead here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 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!

[fkautz]

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.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

[pohly]

Doc PR for 1.30 created and linked to in the description.

[salehsedghpour]

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:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, I couldn't find any (open) PRs in k/k. With this, it is now marked as at risk for code freeze for the v1.30 Code Freeze!

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!

[sreeram-venkitesh]

Hi @pohly 👋, 1.31 Enhancements Lead here.

If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze.

/remove-label lead-opted-in

[SergeyKanzhelev]

/label lead-opted-in
/milestone v1.31
/assign @pohly

[sreeram-venkitesh]

@pohly This KEP is graduating to beta in v1.31, am I correct? Wanted to confirm with you since the other DRA KEP #3063 has multiple stages of alpha/beta.

[pohly]

This and #3063 remain in alpha in 1.31.

[prianna]

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 alpha for v1.31 (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.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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 tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[hacktivist123]

Hello @pohly 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.

Thank you!

[pohly]

@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.

[hacktivist123]

Thanks for the update @pohly

[rashansmith]

Hi @pohly,

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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

[rashansmith]

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.

[prianna]

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:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s 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 are open and need to be merged before code freeze:

• DRA for 1.31 kubernetes#125488

If you anticipate missing code freeze, you can file an exception request in advance.

[prianna]

@hacktivist123 Same question here re: the transition to tracked? It doesn't look like this one is ready either.

[sreeram-venkitesh]

@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)

[pohly]

Yes, kubernetes/kubernetes#125488 is also for this KEP and got merged, so we are good for 1.31.

[sreeram-venkitesh]

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.

[pohly]

kubernetes/kubernetes#120611 is an optional PR for this feature in 1.31. Would be nice to have, but not required.

[sreeram-venkitesh]

Thanks a lot @pohly! Marking this KEP as tracked for code freeze 🎉

[pohly]

The goal is to promote this to beta in 1.32, if possible.