OSDOCS 12580 Enable Dynamic Resource Allocations for openshift #99730
Conversation
openshift-ci
bot
added
the
size/L
|
🤖 Mon Oct 06 20:05:24 - Prow CI generated the docs preview: |
mburke5678
force-pushed
the
nodes-dra
branch
from
6254fdb to
c0735e9
Compare
mburke5678
changed the title
|
@tkashem Can you PTAL? |
_attributes/common-attributes.adoc
Outdated
| // Formerly out-of-cluster layering | ||
| :image-mode-os-out-caps: Out-of-cluster image mode | ||
| :image-mode-os-out-lower: out-of-cluster image mode | ||
| :attribute-based-full: Attribute-Based GPU Allocation in OpenShift with the NVIDIA GPU Operator |
There was a problem hiding this comment.
we should probably omit with the NVIDIA GPU Operator, in 4.20 we are tech previewing Attribute-Based GPU Allocation only so vendors/partners can implement their DRA driver?
|
|
||
| // Taken from https://issues.redhat.com/browse/OCPSTRAT-1756 | ||
| {attribute-based-full} enables pods to request GPUs based on specific device attributes. This attribute-based resource allocation is achieved by the NVIDIA GPU Operator with a DRA driver, such as the NVIDIA Kubernetes DRA driver. This ensures that each pod receives the exact GPU specifications it requires. | ||
|
|
There was a problem hiding this comment.
we don't support Nvidia GPU allocation in 4.20, so we should not probably mention Nvidia or their GPUs
|
|
||
| Device class:: | ||
| A device class is a category of devices that pods can claimed and how to select specific device attributes in claims. Some device drivers contain their own device class, such as the gpu.nvidia.com. Alternatively, an administrator can create device classes. A device class contains a device selector, which is a link:https://cel.dev/[common expression language (CEL)] expression that must evaluate to true if a device satisfies the request. | ||
| + |
There was a problem hiding this comment.
the following specs refer to Nvidia GPU, oh so this will be marked as tech preview doc only?
There was a problem hiding this comment.
The tech preview notice is in the top file (the assembly file). (I made the name change, but haven't committed the changes yet.)
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@asahay19 PTAL |
|
/lgtm |
https://issues.redhat.com/browse/OSDOCS-16432
Link to docs preview:
QE review: