Skip to content

Split Dynamic Resource Allocation into a Resource Management section - #56295

Merged
kubernetes-prow[bot] merged 10 commits into
kubernetes:dev-1.37from
Caesarsage:dra-resource-management-section
Jul 21, 2026
Merged

Split Dynamic Resource Allocation into a Resource Management section#56295
kubernetes-prow[bot] merged 10 commits into
kubernetes:dev-1.37from
Caesarsage:dra-resource-management-section

Conversation

@Caesarsage

Copy link
Copy Markdown
Contributor

Adds a Concepts > Resource Management section and splits the Dynamic Resource Allocation page into purpose-built pages:

  • dynamic-resource-allocation/_index.md : overview, benefits, limitations
  • dra-api.md : API objects & attributes
  • how-dra-works.md : allocation workflow
  • dra-observability.md : metrics, ResourceClaim status, device health, device metadata
  • dra-features.md : optional capabilities
  • device-taints.md : device taints & tolerations

Approach: verbatim content move, then dropped the alpha features / beta features headings, each capability now sits on its topical page with its
{{< feature-state >}} badge carrying the stage, so graduating features get a
home instead of a maturity bucket to reshuffle each release.

Redirects: aliases on the DRA landing preserve the old
/concepts/scheduling-eviction/dynamic-resource-allocation/ URL.

Scope: structure only. Inbound-link repointing and the v1.37 graduation content follow in separate PRs.

Issue

Related to #49899

discussion on slack here https://kubernetes.slack.com/archives/C1J0BPD2M/p1782232560810309

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 28, 2026
@kubernetes-prow kubernetes-prow Bot added this to the 1.37 milestone Jun 28, 2026
@netlify

netlify Bot commented Jun 28, 2026

Copy link
Copy Markdown

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

Name Link
🔨 Latest commit 660c071
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-vnext-staging/deploys/6a5b5bacc81edb0008888844

@kubernetes-prow
kubernetes-prow Bot requested review from klueska and reylejano June 28, 2026 18:05
@kubernetes-prow kubernetes-prow Bot added language/en Issues or PRs related to English language cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 28, 2026
@netlify

netlify Bot commented Jun 28, 2026

Copy link
Copy Markdown

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 660c071
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6a5b5bacc79fba000806273d
😎 Deploy Preview https://deploy-preview-56295--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

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

lmktfy commented Jun 28, 2026

Copy link
Copy Markdown
Member

/label refactor

@kubernetes-prow kubernetes-prow Bot added the refactor Indicates a PR with large refactoring changes e.g. removes files or moves content label Jun 28, 2026
Caesarsage and others added 2 commits July 4, 2026 12:15
…allocation/_index.md

Co-authored-by: Tim Bannister <193443691+lmktfy@users.noreply.github.com>
@Caesarsage
Caesarsage marked this pull request as ready for review July 4, 2026 11:29
@kubernetes-prow kubernetes-prow Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 4, 2026
@kubernetes-prow
kubernetes-prow Bot requested review from pohly and salaxander July 4, 2026 11:29
@Caesarsage

Copy link
Copy Markdown
Contributor Author

Given ++ from the wg-device-management WG https://kubernetes.slack.com/archives/C0409NGC1TK/p1782721132858409

This is a good first step and ready to merge. next will be to repoint broken links

@kubernetes-prow kubernetes-prow Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 15, 2026

@johnbelamaric johnbelamaric left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some tweaks - though I am also OK merging this as-is and then applying these changes in a follow up PR

api_metadata:
- apiVersion: "resource.k8s.io/v1alpha3"
kind: "DeviceTaintRule"
- apiVersion: "resource.k8s.io/v1beta2"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is going GA in 1.37

is not exempt either. An admin using that mode must explicitly tolerate all taints
to access tainted devices.

Device taints and tolerations is controlled by the

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove this paragraph as it is going GA

Consider the following example:

```yaml
apiVersion: scheduling.k8s.io/v1alpha2

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is moving to beta, we probably should update the version here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some part of the site still uses scheduling.k8s.io/v1alpha2 (podgroup-api and gang-scheduling docs), so bumping just this example would be inconsistent, is there a tracking change for the PodGroup beta graduation I should follow?


<!-- body -->

## Extended resource allocation by DRA {#extended-resource}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this feature doesn't really require any special driver support, maybe it should move up to dra-api.md, or we should remove the comment that these features require driver support

The resulting ResourceClaim will contain a request for an `ExactCount` of the
specified number of devices of that DeviceClass.

Extended resource allocation by DRA is controlled by the

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is going GA in 1.37

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

### DistinctAttribute constraint

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this also does not need driver support

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will update the overview from them requiring driver

in the `kube-apiserver` and `kube-controller-manager`.


## DRA device metadata in containers {#device-metadata}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this belongs in dra-features.md not here

Caesarsage and others added 4 commits July 18, 2026 11:39
…allocation/_index.md

Co-authored-by: John Belamaric <jbelamaric@google.com>
…allocation/_index.md

Co-authored-by: John Belamaric <jbelamaric@google.com>
…nagement-section

# Conflicts:
#	content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@kubernetes-prow kubernetes-prow Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 18, 2026
Caesarsage and others added 2 commits July 18, 2026 11:55
…allocation/device-taints.md

Co-authored-by: John Belamaric <jbelamaric@google.com>
…allocation/device-taints.md

Co-authored-by: John Belamaric <jbelamaric@google.com>
@lmktfy

lmktfy commented Jul 18, 2026

Copy link
Copy Markdown
Member

This is not a change to the live site, so I can
/lgtm
/approve

Lazy consensus because it is a big reorganization.

Anyone is welcome to unhold this after 48 hours, or an approver for the English localizations can unhold at any time.
/hold

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 18, 2026
@kubernetes-prow kubernetes-prow Bot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 18, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: fffd5ff0396d960c6ffa88e41092f80a2f90c4e6

@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lmktfy

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@kubernetes-prow kubernetes-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 18, 2026
@Caesarsage

Copy link
Copy Markdown
Contributor Author

Thanks @johnbelamaric

I will make these fixes as a follow-up rather than here, to keep the Lazy consensus. Once this merges, I suggest #56265 (device taints GA) goes in first, then the follow-up on top.

@reylejano

Copy link
Copy Markdown
Member

@pohly , what do you think of the reorg of the DRA docs?

@lmktfy

lmktfy commented Jul 21, 2026

Copy link
Copy Markdown
Member

Lazy consensus expired with no actual objection.
We can revert this change if needed.

/unhold

@kubernetes-prow kubernetes-prow Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 21, 2026
@kubernetes-prow
kubernetes-prow Bot merged commit c583627 into kubernetes:dev-1.37 Jul 21, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. refactor Indicates a PR with large refactoring changes e.g. removes files or moves content size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants