-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CDI Devices to Device Plugin API #42001
Add CDI Devices to Device Plugin API #42001
Conversation
Welcome @elezar! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
This change expands the documentation for the Device Plugin to include the addition of support for CDI Device Names as a feature-gated feature in the 1.28 release. Signed-off-by: Evan Lezar <elezar@nvidia.com>
83efd8d
to
9af46c8
Compare
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
Outdated
Show resolved
Hide resolved
…/device-plugins.md Co-authored-by: Mengjiao Liu <44460091+mengjiao-liu@users.noreply.github.com>
/sig node |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
Fixups welcome (see inline feedback)
LGTM from #42001 (review)
and for docs:
/lgtm
/approve
device plugin defines modifications that must be made to a container's definition to provide | ||
access to the device. These modifications include: | ||
|
||
* annotations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these Annotations or something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think this link is valid. I've updated the link in #42600
|
||
{{< note >}} | ||
The processing of the fully-qualified CDI device names by the Device Manager requires | ||
the `DevicePluginCDIDevices` feature gate to be enabled. This was added as an alpha feature in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd prefer something like
- the `DevicePluginCDIDevices` feature gate to be enabled. This was added as an alpha feature in
+ that the `DevicePluginCDIDevices` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+ is enabled for the kubelet and the kube-apiserver. This was added as an alpha feature in Kubernetes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in #42600
LGTM label has been added. Git tree hash: 505e01498056373addc2f9c419b8054718175e4f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim, Vikash-8090-Yadav 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:
Approvers can indicate their approval by writing |
…evice-plugin-api Add CDI Devices to Device Plugin API
These changes are a follow-up to kubernetes#42001. They make minor edits to the documentation of the DevicePlugin API. Signed-off-by: Evan Lezar <elezar@nvidia.com>
This change expands the documentation for the Device Plugin to include
the addition of support for CDI Device Names as a feature-gated feature
in the 1.28 release as part of KEP-4009.