Skip to content

25.10 update with govReady release note and openshift mig-back vgpu support #304

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 28, 2025
Merged

25.10 update with govReady release note and openshift mig-back vgpu support #304

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36eb8ef
fix mig-back support, add govReady release note
a-mccarthy Oct 28, 2025
bc62208
Update release notes
a-mccarthy Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions gpu-operator/release-notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,9 @@ Refer to the :ref:`GPU Operator Component Matrix` for a list of software compone
New Features
------------

* The NVIDIA GPU Operator now supports government ready components for NVIDIA AI Enterprise customers.
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>`_.

* Updated software component versions:

- NVIDIA Driver Manager for Kubernetes v0.9.0
Expand Down
14 changes: 7 additions & 7 deletions openshift/openshift-virtualization.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,8 +91,6 @@ Assumptions, constraints, and dependencies

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

* MIG-backed vGPUs are not supported.

* The GPU Operator will not automate the installation of the vGPU guest driver inside KubeVirt VMs with vGPUs attached.

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

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


.. note::

On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances.
To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.


The following example shows a system with two **A10** GPUs.

.. code-block:: console
Expand Down Expand Up @@ -725,8 +730,3 @@ You should now see 12 **A10-4Q** devices on the node, as 6 **A10-4Q** devices ca
{
"nvidia.com/NVIDIA_A10-4Q": "12"
}

.. note::

On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances.
To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.