Re: Exception for KEP 4381: DRA structured parameters

[Mrunal]

+1 from sig-node.

On Thu, Mar 20, 2025 at 12:36 PM 'Morten Torkildsen' via kubernetes-sig-node <kubernete...@googlegroups.com> wrote:

Hi all,

I would like to request an exception for 1.33.

• Enhancement name: DRA structured parameters
• Enhancement status (alpha/beta/stable): beta
• SIG: Node, Scheduling
• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/4381
• PR #’s:
• https://github.com/kubernetes/kubernetes/pull/129970
• The PR is in review but needs more time for API review and for some final naming decisions.
• Additional time needed (in days): 6 (including weekend; merge by Wed next week)
• Reason this enhancement is critical for this milestone:
• The main functionality is already beta and has only had incremental improvements in this cycle. However, there are related alpha KEPs (DRA Prioritized List, DRA Device Taints, DRA Partitionable Devices), which have already merged with new fields in the v1beta1 API.
• We want to create an updated v1beta2 API that provides a more cohesive user experience and will provide a cleaner, safer path with little to no changes when we go from beta to GA.
• The PR we need an extension for is just that new API. The PR couldn’t really be completed until those other implementations merged (which they have now).
• Risks from adding code late: (to k8s stability, testing, etc.):
• Risks are minimal and affect only the DRA ResourceClaim and ResourceSlice APIs. Addition of the v1beta2 API mostly adds conversion logic, but does touch some internal API types. These APIs are well covered with extensive unit tests, plus integration and e2e tests, so that mitigates the risks of touching this code.
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.):
• Bringing DRA to GA in 1.34 is a critical priority for the project as it is in very high demand for our AI/ML use cases. Missing v1beta2 in 1.33 will require us to either delay that GA, or to take on additional risk during GA promotion to implement the API conversions at that time.

Morten

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-node/CAFm6J6cbUvO6JabhWo8mV5XNuBxE%2BZHbGMPy7agdM4AuJYokJw%40mail.gmail.com.

[John Belamaric]

+1 to this exception. This aligns with what we discussed pretty extensively in SIG Arch and in Composability in ResourceSlice APIs, and is low risk.

Thank you.

[Morten Torkildsen]

[Patrick Ohly]

"'Morten Torkildsen' via kubernetes-sig-node"
<kubernete...@googlegroups.com> writes:
> - We want to create an updated v1beta2 API that provides a more

> cohesive user experience and will provide a cleaner, safer path
> with little
> to no changes when we go from beta to GA.

+1

We want this and couldn't really do it sooner because the other changes
for 1.33 had to be merged first.

--
Best Regards

Patrick Ohly
Cloud Software Architect

[nina polshakova]

Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge all PRs for your KEP is 8:00 PDT on Wednesday, 26th March 2025.

If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Nina Polshakova
1.33 Release Team Lead

[0] https://kubernetes.slack.com/archives/C2C40FMNF/p1742516740311229 

[Dominik Marciński]

+1

Adding sig-scheduler approvers +Maciej Skoczeń +sanposhiho

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-scheduling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-sch...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-scheduling/yrjh5xk2dfvj.fsf%40pohly-mobl1.fritz.box.