search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.42k stars 1.47k forks source link

DRA: structured parameters #4381

Open pohly opened 9 months ago

pohly commented 9 months ago

Enhancement Description

pohly commented 9 months ago

/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 commented 8 months ago

/stage alpha /milestone v1.30

klueska commented 8 months ago

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

k8s-ci-robot commented 8 months ago

@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](https://github.com/kubernetes/enhancements/issues/4381#issuecomment-1933059051): >/milestone v1.30 >/label lead-opted-in Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
johnbelamaric commented 8 months ago

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

johnbelamaric commented 8 months ago

/label lead-opted-in

k8s-ci-robot commented 8 months ago

@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](https://github.com/kubernetes/enhancements/issues/4381#issuecomment-1933059051): >/milestone v1.30 >/label lead-opted-in Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
SergeyKanzhelev commented 8 months ago

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

salehsedghpour commented 8 months ago

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:

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:

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 commented 8 months ago

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

drewhagen commented 8 months ago

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 commented 8 months ago

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 commented 7 months ago

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

salehsedghpour commented 7 months ago

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

salehsedghpour commented 7 months ago

Hello @pohly 👋 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.30 milestone.

If you still wish to progress this enhancement in v1.30, please file an exception request. Thanks!

/milestone clear

salehsedghpour commented 7 months ago

With the exception request being approved, this can now be marked as tracked for code freeze

/milestone v1.30

sreeram-venkitesh commented 5 months ago

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 commented 4 months ago

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

sreeram-venkitesh commented 4 months ago

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

pohly commented 4 months ago

This and #3063 remain in alpha in 1.31.

prianna commented 4 months ago

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:

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 commented 4 months ago

Hello @pohly :wave:, 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 commented 4 months ago

@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 commented 4 months ago

Thanks for the update @pohly

rashansmith commented 3 months ago

Hi @pohly,

:wave: 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 commented 3 months ago

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 commented 3 months ago

Hey again @pohly 👋 Enhancements team here,

To avoid repeating myself too much (see https://github.com/kubernetes/enhancements/issues/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.

prianna commented 2 months ago

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

sreeram-venkitesh commented 2 months ago

@pohly Is merging https://github.com/kubernetes/kubernetes/pull/125488 related to this KEP? I could only find another PR, https://github.com/kubernetes/kubernetes/pull/120611 related to this KEP. Please let us know if we should be tracking any other PRs as well.

Ref: https://github.com/kubernetes/enhancements/issues/3063#issuecomment-2244502596

pohly commented 2 months ago

Yes, https://github.com/kubernetes/kubernetes/pull/125488 is also for this KEP and got merged, so we are good for 1.31.

sreeram-venkitesh commented 2 months ago

Awesome, thanks a lot. Are we good to mark this KEP as tracked for code freeze? I'm also curious to know where https://github.com/kubernetes/kubernetes/pull/120611 comes into picture.

pohly commented 2 months ago

https://github.com/kubernetes/kubernetes/pull/120611 is an optional PR for this feature in 1.31. Would be nice to have, but not required.

sreeram-venkitesh commented 2 months ago

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

pohly commented 1 month ago

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

tjons commented 1 month ago

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

haircommander commented 4 weeks ago

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

impact-maker commented 2 weeks ago

Hello @haircommander @pohly 👋, 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!

edithturn commented 2 days ago

Hello @pohly , 👋🏼 this is Edith from the v1.32 Communications Team!

We’d love for you to consider writing 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 30th Oct 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.

hacktivist123 commented 1 day ago

Hello @pohly 👋 1.32 Docs Shadow here.

Does this enhancement work planned for 1.32 require any new docs or modifications to existing docs? If so, please follow the steps here to open a PR against the 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!