DRA: relocate extended-resource and device-metadata sections - #56642
Merged
kubernetes-prow[bot] merged 1 commit intoAug 5, 2026
Merged
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
kubernetes-prow
Bot
added
the
language/en
kubernetes-prow
Bot
added
cncf-cla: yes
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
/wg device-management |
kubernetes-prow
Bot
added
the
wg/device-management
Member
|
/label refactor /lgtm |
kubernetes-prow
Bot
added
the
refactor
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
LGTM label has been added. DetailsGit tree hash: 5bd3ac448fcb14b7aa12bdfd0abfc718f152e503 |
4 tasks
kubernetes-prow
Bot
added
needs-rebase
kubernetes-prow
Bot
removed
the
needs-rebase
lmktfy
reviewed
Aug 4, 2026
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
LGTM label has been added. DetailsGit tree hash: 968eb0f75a14d51acd5c1fb41286925cfee42569 |
kubernetes-prow
Bot
added
the
approved
Member
|
Oops, there's a merge conflict. |
kubernetes-prow
Bot
added
needs-rebase
…n driver-support framing Signed-off-by: caesarsage <destinyerhabor6@gmail.com>
Caesarsage
force-pushed
the
dra-review-followup
branch
from
August 5, 2026 07:39
046cd0a to
f1e18f8
Compare
kubernetes-prow
Bot
removed
the
lgtm
kubernetes-prow
Bot
removed
the
needs-rebase
Contributor
Author
Thanks, I have rebased |
Contributor
|
/lgtm /assign @lmktfy |
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
LGTM label has been added. DetailsGit tree hash: 369945105bc58e1879949d9613147504ee945a3b |
lmktfy
approved these changes
Aug 5, 2026
lmktfy
left a comment
lmktfy
left a comment
Member
There was a problem hiding this comment.
This change makes our docs better.
/approve
Member
There was a problem hiding this comment.
(aside)
We could hyperlink to this from https://kubernetes.io/docs/concepts/cluster-administration/observability/
Comment on lines
+487
to
+523
| ### Device metadata protocol {#device-metadata-protocol} | ||
|
|
||
| The protocol consists of four rules: | ||
|
|
||
| 1. **File paths.** Metadata files live inside containers under | ||
| `/var/run/kubernetes.io/dra-device-attributes`. For a directly referenced | ||
| ResourceClaim the path is | ||
| `resourceclaims/<claimName>/<requestName>/<driverName>-metadata.json`; for a | ||
| claim created from a ResourceClaimTemplate the path is | ||
| `resourceclaimtemplates/<podClaimName>/<requestName>/<driverName>-metadata.json` | ||
| (where `podClaimName` is `pod.spec.resourceClaims[].name`). | ||
|
|
||
| In cases where the ResourceClaim request uses the | ||
| [prioritized list](#prioritized-list) feature, only the top-level request | ||
| name is used for the `<requestName>` segment in the file path (that is, | ||
| the `/<subrequest>` portion is dropped). Inside the | ||
| JSON file, the `requests[].name` field carries the full | ||
| `<request>/<subrequest>` reference (for example, `gpu/high-memory`) so | ||
| that consumers can identify which alternative was allocated. | ||
|
|
||
| The path constants are defined in | ||
| [`k8s.io/dynamic-resource-allocation/api/metadata`](https://pkg.go.dev/k8s.io/dynamic-resource-allocation/api/metadata). | ||
|
|
||
| 1. **JSON API.** Each file is a stream of one or more | ||
| [`DeviceMetadata`](https://pkg.go.dev/k8s.io/dynamic-resource-allocation/api/metadata/v1alpha1#DeviceMetadata) | ||
| objects serialized as versioned JSON with `apiVersion` and `kind`, following | ||
| Kubernetes API conventions. The same metadata is encoded once per supported | ||
| API version (newest first). All objects in the stream are semantically | ||
| equivalent; consumers should use the first object they can decode. | ||
|
|
||
| 1. **Generation.** When a driver updates a metadata file the embedded | ||
| `metadata.generation` field must increase so consumers can detect changes. | ||
|
|
||
| 1. **Container exposure.** Files are typically exposed via | ||
| {{< glossary_tooltip text="CDI" term_id="cdi" >}} bind-mounts, but other | ||
| mechanisms are permitted as long as the file appears at the correct path and | ||
| is read-only inside the container. |
Member
There was a problem hiding this comment.
IMO we could eventually move this inside https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/ - but with a lot of signposting and other work to make the move low friction for people reading the docs.
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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #56295 addressing review feedback.
DeviceTaintRule API version was left out — already handled by #56265.