[KEP-5075] DRAConsumableCapacity documentation

[sunya-ch]

Description

Docs change for KEP-5075.

Issue

kubernetes/enhancements: kubernetes/enhancements#5075
kubernetes/kubernetes: kubernetes/kubernetes#132522

[k8s-ci-robot]

Welcome @sunya-ch!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2f8244a
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/689007652ec1c100081b6643
😎 Deploy Preview	https://deploy-preview-51479--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lmktfy]

/hold

I think this should target the dev-1.34 branch.
Does that sound right?

OK to unhold once target branch is confirmed.

[sunya-ch]

@lmktfy Thank you so much for the review. I have rebased to dev-1.34 and committed your suggestions.

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	2f8244a
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-vnext-staging/deploys/68900765471f270008e2d33d

[sunya-ch]

Resolved conflict and updated example according to latest API review.

• sharingPolicy --> requestPolicy
• capacityRequests.minimum --> capacity.requests
• validRange.minimum --> validRange.min
• validRange.chunkSize --> validRange.step
• consumedCapacities --> consumedCapacity

[johnbelamaric]

This is not required, right? This would limit the chose of device to ONLY those with consumable capacity. Let's leave it out of the basic example. Then, after your example allocation, I would add the paragraph:

In this example, a multiply-allocatable device was chosen. However, any resource.example.com device with at least the requested 1G bandwidth could have met the requirement. If a non-multiply-allocatable device were chosen, the allocation would have resulted in the entire device. To force the use of a only multiply-allocatable devices, you can use the CEL criteria device.allowMultipleAllocations == true.

[sunya-ch]

@johnbelamaric Thank you so much for your review and suggestions.
I have applied your suggestions here: https://github.com/kubernetes/website/compare/daec5a57dc2854717d08c33b7b2ef78a0c3f6e7b..f183ec7b3c9c2692fda288435c1e279386398432.

[michellengnx]

Hello @sunya-ch 👋! I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on Wednesday August 6, 2025 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. Thank you!

[johnbelamaric]

/approve

[johnbelamaric]

/hold cancel

[natalisucks]

@sunya-ch thanks for this work!
@johnbelamaric Only SIG Docs approvers have the ability to add the approve label on docs PRs – would you mind adding your LGTM?
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnbelamaric, natalisucks

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS [natalisucks]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[natalisucks]

ah, i missed that John is good to go for tech reviews on DRA content, adding the other label as well so we get things in for Docs Freeze
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1cb78d40ee918e4f19d519493bd65fab182454f1

[johnbelamaric]

@johnbelamaric Only SIG Docs approvers have the ability to add the approve label on docs PRs – would you mind adding your LGTM?

Yeah, I was using "approve" here for tech review approval, even though it has no effect from a tooling viewpoint

[sunya-ch]

@natalisucks @johnbelamaric

I apologize for the oversight — I just noticed a mistake in this document after the merge and would like to add the below change. How should I proceed?

diff --git a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
index f9af94c36a..9ed9bccf88 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -588,8 +588,7 @@ spec:
       requests:
       - name: req-0
         exactly:
-        - name:
-          deviceClassName: resource.example.com
+        - deviceClassName: resource.example.com

[johnbelamaric]

I apologize for the oversight — I just noticed a mistake in this document after the merge and would like to add the below change. How should I proceed?

Send a follow-up PR if you have not already