Skip to content

Commit 5435e5c

Browse files
authored
25.10 update with govReady release note and openshift mig-back vgpu support (#304)
* fix mig-back support, add govReady release note Signed-off-by: Abigail McCarthy <[email protected]> * Update release notes Signed-off-by: Abigail McCarthy <[email protected]> --------- Signed-off-by: Abigail McCarthy <[email protected]>
1 parent 8105af6 commit 5435e5c

File tree

2 files changed

+10
-7
lines changed

2 files changed

+10
-7
lines changed

gpu-operator/release-notes.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,9 @@ Refer to the :ref:`GPU Operator Component Matrix` for a list of software compone
4141
New Features
4242
------------
4343

44+
* The NVIDIA GPU Operator now supports government ready components for NVIDIA AI Enterprise customers.
45+
Government ready is NVIDIA's designation for software that meets applicable security requirements for deployment in your FedRAMP High or equivalent sovereign use case. For more information on NVIDIA's government ready support, refer to the :ref:`install-gpu-operator-gov-ready` deployment guide or the `AI Software for Regulated Environments White Paper <https://docs.nvidia.com/ai-enterprise/planning-resource/ai-software-regulated-environments-white-paper/latest/index.html>`_.
46+
4447
* Updated software component versions:
4548

4649
- NVIDIA Driver Manager for Kubernetes v0.9.0

openshift/openshift-virtualization.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,6 @@ Assumptions, constraints, and dependencies
9191

9292
* Worker nodes running GPU accelerated VMs (with pGPU or vGPU) are assumed to be bare metal.
9393

94-
* MIG-backed vGPUs are not supported.
95-
9694
* The GPU Operator will not automate the installation of the vGPU guest driver inside KubeVirt VMs with vGPUs attached.
9795

9896
* There are two separate device plugins – the NVIDIA k8s-device-plugin and the NVIDIA kubevirt-gpu-device-plugin.
@@ -682,6 +680,13 @@ Switching vGPU device configuration after one has been successfully applied assu
682680

683681
To apply a new configuration after GPU Operator install, simply update the ``nvidia.com/vgpu.config`` node label.
684682

683+
684+
.. note::
685+
686+
On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances.
687+
To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.
688+
689+
685690
The following example shows a system with two **A10** GPUs.
686691

687692
.. code-block:: console
@@ -725,8 +730,3 @@ You should now see 12 **A10-4Q** devices on the node, as 6 **A10-4Q** devices ca
725730
{
726731
"nvidia.com/NVIDIA_A10-4Q": "12"
727732
}
728-
729-
.. note::
730-
731-
On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances.
732-
To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.

0 commit comments

Comments
 (0)