Exception Request for KEP-5075 Implementation

[SUNYANAN CHOOCHOTKAEW]

• Enhancement name:
• DRA Consumable Capacity
• Enhancement status (alpha/beta/stable):
• alpha
• SIG:
• Scheduling (, Node, Network)
• k/enhancements repo issue #:
• https://github.com/kubernetes/enhancements/issues/5075
• PR #’s:
• https://github.com/kubernetes/kubernetes/pull/132522
• Additional time needed (in days):
• 7 days (until Jul 31)
• Reason this enhancement is critical for this milestone:
• There are concrete use cases that require this enhancement.
• Risks from adding code late: (to k8s stability, testing, etc.)
• This enhancement uses a feature gate mechanism and is disabled by default, so the risk remains low even if it is added later.
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
• Delaying this will significantly slow down adoption of DRA in the use case that requires an ability to allocate a shareable device via DRA multiple – especially when pre-defined partitions are not viable (for example, because there would be too many of them). A solid example is network device sharing via DRA to support MACVLAN/IPVLAN.

Thanks for your consideration.

 

[Patrick Ohly]

"'SUNYANAN CHOOCHOTKAEW' via kubernetes-sig-release"
<kubernetes-...@googlegroups.com> writes:
> * Risks from adding code late: (to k8s stability, testing, etc.)
> * This enhancement uses a feature gate mechanism and is

> disabled by default, so the risk remains low even if it is added
> later.

We are also very careful about putting several of the complex changes into a
completely separate package which is not called at all when non-alpha
features are disabled.

+1 for the DRA side.

--
Best Regards

Patrick Ohly
Cloud Software Architect

Intel Deutschland GmbH
System Software Engineering/Cloud Native
Usenerstr. 5a Phone: +49-228-2493652
53129 Bonn
Germany

[John Belamaric]

+1 from me too

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

[Vyom Yadav]

The release team is APPROVING the exception request. The new deadline to get the relevant changes in is 02:00 UTC, 1st August.  Slack Discussion: https://kubernetes.slack.com/archives/C2C40FMNF/p1753431535519959  

[SUNYANAN CHOOCHOTKAEW]

• Enhancement name:

• DRA Consumable Capacity

• Enhancement status (alpha/beta/stable):

• alpha

• SIG:

• Scheduling

• k/enhancements repo issue #:

• https://github.com/kubernetes/enhancements/issues/5075

• PR #’s:

• https://github.com/kubernetes/website/pull/51919

• Additional time needed (in days):

• 4 days (until Aug 18)

• Reason this enhancement is critical for this milestone:

• The example contains a significant error.

• Risks from adding code late: (to k8s stability, testing, etc.)

• No risk to the code.

• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

• It may mislead or confuse the reader regarding the API.
  
  

Thanks for your consideration.

 

[Vyom Yadav]

Hey Folks,

The release team is APPROVING this docs exception request based on the discussion in the Slack thread[0]. 

Your updated deadline to merge docs PR is 16:00 PST 18th July.

Also, for the future, kindly start a separate thread for docs freeze-related exception requests.

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

Thanks,
Vyom Yadav
v1.34 Release Team Lead

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