Skip to content

fix: Post-release updates #478

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

Open
mikemckiernan wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: Post-release updates #478

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
2394ca8
fix: Post-release updates
mikemckiernan Aug 24, 2026
3601166
chore: per-patch-release third-party notices
mikemckiernan Aug 25, 2026
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
8 changes: 4 additions & 4 deletions gpu-operator/getting-started.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Prerequisites
For worker nodes or node groups that run CPU workloads only, the nodes can run any operating system because
the GPU Operator does not perform any configuration or management of nodes for CPU-only workloads.

If you are planning to use NVIDIA GPU Driver Custom Resource Definition, you can use a mix of operating system versions on CPU and GPU nodes. Refer to the :doc:`NVIDIA GPU Driver Custom Resource Definition <gpu-driver-configuration>` page for more information.
If you are planning to use NVIDIA GPU Driver Custom Resource Definition, you can use a mix of operating system versions on CPU and GPU nodes. Refer to the :doc:`NVIDIA Driver Custom Resource Definition <nvidia-driver-configuration>` page for more information.

#. Nodes must be configured with a container engine such as CRI-O or containerd.

Expand Down Expand Up @@ -470,7 +470,7 @@ To view all the options, run ``helm show values nvidia/gpu-operator``.

* - ``driver.nvidiaDriverCRD.enabled``
- When set to ``true``, the Operator deploys NVIDIA GPU Driver Custom Resource Definition.
Refer to the :doc:`NVIDIA GPU Driver Custom Resource Definition <gpu-driver-configuration>` page for more information.
Refer to the :doc:`NVIDIA Driver Custom Resource Definition <nvidia-driver-configuration>` page for more information.
- ``false``

* - ``driver.repository``
Expand Down Expand Up @@ -540,7 +540,7 @@ To view all the options, run ``helm show values nvidia/gpu-operator``.
When set to ``true``, the GDRCopy Driver runs as a sidecar container in the GPU driver pod.
For information about GDRCopy, refer to the `gdrcopy <https://developer.nvidia.com/gdrcopy>`__ page.

You can enable GDRCopy if you use the :doc:`gpu-driver-configuration`.
You can enable GDRCopy if you use the :doc:`nvidia-driver-configuration`.
- ``false``


Expand Down Expand Up @@ -899,6 +899,6 @@ After verifying the installation, you can configure the GPU Operator for your wo
- :doc:`gpu-operator-mig` — Configure Multi-Instance GPU (MIG) partitioning on supported GPUs.
- :doc:`gpu-operator-rdma` — Enable GPUDirect RDMA for high-performance networking.
- :doc:`dra-intro-install` — Allocate GPUs by using Kubernetes Dynamic Resource Allocation (DRA).
- :doc:`gpu-driver-configuration` — Use the NVIDIA GPU Driver Custom Resource Definition to manage drivers per node.
- :doc:`nvidia-driver-configuration` — Use the NVIDIA GPU Driver Custom Resource Definition to manage drivers per node.
- :doc:`precompiled-drivers` — Speed up driver deployments with precompiled kernel modules.
- :doc:`cdi` — Learn about Container Device Interface (CDI) and NRI Plugin mode.
5 changes: 5 additions & 0 deletions gpu-operator/gpu-operator-kubevirt-dra.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,6 +269,11 @@ Verify DRA Resources

$ kubectl get resourceslice <slice-name> -o yaml

The driver publishes partition membership through attributes named ``partitionN``,
where ``N`` is ``1``, ``2``, ``4``, or ``8`` and specifies the number of GPUs in the partition.
The attribute value is the Fabric Manager partition ID.
For example, ``partition2: 4`` indicates that the GPU belongs to two-GPU partition 4.

Confirm that devices with the ``gpu.nvidia.com/type`` attribute set to
``vfio`` include a ``gpuModuleID`` attribute and the ``partitionN`` attributes
reported for the hardware. For the two-GPU example in this procedure, at
Expand Down
2 changes: 1 addition & 1 deletion gpu-operator/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@
Outdated Kernels <install-gpu-operator-outdated-kernels.rst>
Custom GPU Driver Parameters <custom-driver-params.rst>
precompiled-drivers.rst
GPU Driver CRD <gpu-driver-configuration.rst>
NVIDIA Driver CRD <nvidia-driver-configuration.rst>

@rahulait rahulait Aug 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make it NVIDIADriver with no space and page to nvidiadriver-configuration.rst? Folks might use full name nvidiadriver in searches and all and keeping space or - will not give them right results.

@mikemckiernan mikemckiernan Aug 24, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like that would harm readability, esp in a TOC. The "CRD" ought to help.

In general, plain text is the clearest to read. I feel like the OCP folks did a thoughtful review on the topic: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#api-object-formatting

CDI and NRI Support <cdi.rst>

.. toctree::
Expand Down
12 changes: 6 additions & 6 deletions gpu-operator/life-cycle-policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ NVIDIA GPU Operator Versioning
NVIDIA GPU Operator is versioned following the calendar versioning convention.

The version follows the pattern ``YY.MM.PP``, such as 23.6.0, 23.6.1, and 23.9.0.
The first two fields, ``YY.MM`` identify a major version and indicates when the major version was initially released.
The first two fields, ``YY.MM``, identify a major version and indicate when the major version was initially released.
The third field, ``PP``, identifies the patch version of the major version.
Patch releases typically include critical bug and CVE fixes, but can include minor features.

Expand All @@ -39,7 +39,7 @@ NVIDIA GPU Operator Life Cycle
******************************

When a new major version of NVIDIA GPU Operator is released, the previous major version enters deprecated support and only receives patch release updates for critical bug and CVE fixes.
All prior major versions enter end of support and are no longer supported and do not receive patch release updates.
All prior major versions reach end of support and no longer receive patch release updates.

The product life cycle and versioning are subject to change in the future.

Expand All @@ -53,7 +53,7 @@ The product life cycle and versioning are subject to change in the future.
* - GPU Operator Version
- Status

* - 26.6.x
* - 26.7.x
- Supported

* - 26.3.x
Expand All @@ -80,7 +80,7 @@ When post-release testing confirms support for newer versions of operands, these
Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.

.. note::
All the following components are supported as :ref:`government-ready <install-gpu-operator-gov-ready>` in the NVIDIA GPU Operator v26.3, except for NVIDIA GDS Driver, NVIDIA Confidential Computing Manager, and NVIDIA GDRCopy Driver.
All of the following components are supported as :ref:`government-ready <install-gpu-operator-gov-ready>` in the NVIDIA GPU Operator v26.7, except for NVIDIA GDS Driver, NVIDIA Confidential Computing Manager, and NVIDIA GDRCopy Driver.

**D** = Default driver, **R** = Recommended driver

Expand Down Expand Up @@ -127,10 +127,10 @@ Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.
- ${version}

* - NVIDIA KubeVirt GPU Device Plugin
- `v1.5.0 <https://github.com/NVIDIA/kubevirt-gpu-device-plugin>`__
- `v1.6.0 <https://github.com/NVIDIA/kubevirt-gpu-device-plugin>`__

* - NVIDIA vGPU Device Manager
- `v0.4.2 <https://github.com/NVIDIA/vgpu-device-manager>`__
- `v0.5.0 <https://github.com/NVIDIA/vgpu-device-manager>`__

* - NVIDIA GDS Driver |gds|_
- `2.29.4 <https://github.com/NVIDIA/gds-nvidia-fs/releases>`__
Expand Down
31 changes: 18 additions & 13 deletions gpu-operator/gpu-driver-configuration.rst → gpu-operator/nvidia-driver-configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,18 @@

.. headings (h1/h2/h3/h4/h5) are # * = -

############################################
NVIDIA GPU Driver Custom Resource Definition
############################################
.. _nvidia-gpu-driver-custom-resource-definition:

########################################
NVIDIA Driver Custom Resource Definition
########################################

*****************************************************
Overview of the GPU Driver Custom Resource Definition
*****************************************************

.. _overview-of-the-gpu-driver-custom-resource-definition:

********************************************************
Overview of the NVIDIA Driver Custom Resource Definition
********************************************************

You can create one or more instances of an NVIDIA driver (``NVIDIADriver``) custom resource
to specify the NVIDIA GPU driver type and driver version to configure on specific nodes.
Expand Down Expand Up @@ -161,7 +165,7 @@ Custom Driver Parameters
For more information, refer to :doc:`Customizing NVIDIA GPU Driver Parameters during Installation <custom-driver-params>`.


.. _migrate-clusterpolicy-to-nvidiadriver:
.. _migrating-from-cluster-policy-driver-management:

***********************************************
Migrating from Cluster Policy Driver Management
Expand Down Expand Up @@ -348,8 +352,8 @@ The following table describes some of the fields in the custom resource.

* - ``kernelModuleType``
- Specifies the type of the NVIDIA GPU Kernel modules to use.
Valid values are ``auto`` (default), ``proprietary``, and ``open``.
Valid values are ``auto`` (default), ``proprietary``, and ``open``.

``Auto`` means that the recommended kernel module type is chosen based on the GPU devices on the host and the driver branch used.
- ``auto``

Expand Down Expand Up @@ -384,7 +388,7 @@ The following table describes some of the fields in the custom resource.
- ``nvcr.io/nvidia``

* - ``useOpenKernelModules`` Deprecated.
- This field is deprecated as of v25.3.0 and will be ignored. Use ``kernelModuleType`` instead.
- This field is deprecated as of v25.3.0 and will be ignored. Use ``kernelModuleType`` instead.
Specifies to use the NVIDIA Open GPU Kernel modules.
- ``false``

Expand Down Expand Up @@ -576,10 +580,11 @@ Precompiled Driver Container on Some Nodes


.. _nvd-upgrade:
.. _upgrading-the-nvidia-gpu-driver:

*******************************
Upgrading the NVIDIA GPU Driver
*******************************
***************************
Upgrading the NVIDIA Driver
***************************

To upgrade a driver managed by an NVIDIA driver custom resource, update the ``spec.version`` field.
The upgrade controller applies the resource's ``spec.upgradePolicy`` to the nodes that it manages.
Expand Down
76 changes: 58 additions & 18 deletions gpu-operator/overview.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,94 +72,134 @@ more information on how to contribute and the release artifacts.
The base images used by the software might include software that is licensed under open-source licenses such as GPL.
The source code for these components is archived on the CUDA opensource `index <https://developer.download.nvidia.com/compute/cuda/opensource/>`_.

The following table identifieis the licenses for the Operator and software components.
The following table identifies the licenses for the Operator and software components.
By installing and using the GPU Operator, you accept the terms and conditions of these licenses.

.. list-table::
:header-rows: 1
:widths: 25 10 40 25
:widths: 30 10 60

* - Component
- Artifact Type
- Artifact Licenses
- Third-Party Licenses

* - NVIDIA GPU Operator
- Helm Chart
- `Apache 2.0 <https://www.apache.org/licenses/LICENSE-2.0>`__
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/gpu-operator/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA GPU Operator
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/gpu-operator/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA GPU Driver
- Image
- `License for Customer Use of NVIDIA Software <http://www.nvidia.com/content/DriverDownload-March2009/licence.php?lang=us>`__

|pstai|_
- --

* - NVIDIA Container Toolkit
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/nvidia-container-toolkit/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA Kubernetes Device Plugin
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-device-plugin/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA MIG Manager for Kubernetes
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/mig-parted/blob/main/THIRD_PARTY_NOTICES.md>`__

* - Validator for NVIDIA GPU Operator
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/gpu-operator/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA DCGM
- Image
- |pstai|_
- --

* - NVIDIA DCGM Exporter
- Image
- |pstai|_
- --

* - NVIDIA Driver Manager for Kubernetes
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-driver-manager/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA KubeVirt GPU Device Plugin
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/kubevirt-gpu-device-plugin/blob/master/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA vGPU Device Manager
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/vgpu-device-manager/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA GDS Driver
- Image
- `License for Customer Use of NVIDIA Software <http://www.nvidia.com/content/DriverDownload-March2009/licence.php?lang=us>`__

|pstai|_
- --

* - NVIDIA Confidential Computing
Manager for Kubernetes
- Image
- |pstai|_
- `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-cc-manager/blob/main/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA GDRCopy Driver
- Image
- |pstai|_
- `Third-Party Notices <https://catalog.ngc.nvidia.com/orgs/nvidia/cloud-native/containers/gdrdrv/->`__


Third-Party Notices by GPU Operator Release
-------------------------------------------

The following table maps each GPU Operator patch release to the exact component release and third-party notices.

.. flat-table::
:header-rows: 2

* - :rspan:`1` Component
- GPU Operator Version

* - v26.7.0

* - NVIDIA GPU Operator Helm chart and image
- | v26.7.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/gpu-operator/blob/v26.7.0/THIRD_PARTY_NOTICES.md>`__

* - Validator for NVIDIA GPU Operator
- | v26.7.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/gpu-operator/blob/v26.7.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA Container Toolkit
- | v1.20.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/nvidia-container-toolkit/blob/v1.20.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA Kubernetes Device Plugin
- | v0.20.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-device-plugin/blob/v0.20.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA MIG Manager for Kubernetes
- | v0.15.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/mig-parted/blob/v0.15.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA Driver Manager for Kubernetes
- | v0.12.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-driver-manager/blob/v0.12.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA KubeVirt GPU Device Plugin
- | v1.6.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/kubevirt-gpu-device-plugin/blob/v1.6.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA vGPU Device Manager
- | v0.5.0
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/vgpu-device-manager/blob/v0.5.0/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA Confidential Computing
Manager for Kubernetes
- | v0.4.3
| `THIRD_PARTY_NOTICES.md <https://github.com/NVIDIA/k8s-cc-manager/blob/v0.4.3/THIRD_PARTY_NOTICES.md>`__

* - NVIDIA GDRCopy Driver
- | v2.6
| The notices are published with each operating-system-specific image in the `NGC Catalog <https://catalog.ngc.nvidia.com/orgs/nvidia/cloud-native/containers/gdrdrv/->`__.
Select the image tag that matches your host operating system.
15 changes: 11 additions & 4 deletions gpu-operator/platform-support.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,7 +331,7 @@ Bare Metal / Virtual Machines with GPU Passthrough and NVIDIA vGPU
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36
- 1.33---1.35
- 1.33---1.36
- 2.17

* - Ubuntu 24.04 LTS
Expand All @@ -341,7 +341,7 @@ Bare Metal / Virtual Machines with GPU Passthrough and NVIDIA vGPU
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36
- 1.33---1.35
- 1.33---1.36
- 2.17

* - Ubuntu 22.04 LTS |fn2|_
Expand All @@ -351,7 +351,7 @@ Bare Metal / Virtual Machines with GPU Passthrough and NVIDIA vGPU
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36
- 1.33---1.35
- 1.33---1.36
- 2.15 2.16 2.17

* - Red Hat Core OS
Expand Down Expand Up @@ -483,18 +483,23 @@ Cloud Service Providers
| Kubernetes
- | Google GKE
| Kubernetes
- | Microsoft Azure
| Kubernetes Service

* - Ubuntu 26.04 LTS
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36

* - Ubuntu 24.04 LTS
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36

* - Ubuntu 22.04 LTS
- 1.33---1.36
- 1.33---1.36
- 1.33---1.36

.. _supported-precompiled-drivers:

Expand Down Expand Up @@ -558,14 +563,16 @@ To report an issue with the GPU Operator on one of these configurations, open an

For more details about partners and their supported configurations, refer to the :external+pv:doc:`index` page.

.. _supported-container-runtimes:

****************************
Supported Container Runtimes
****************************

The GPU Operator has been validated for the following container runtimes:

+----------------------------+------------------------+----------------+
| Operating System | Containerd 1.8 - 2.3 | CRI-O |
| Operating System | Containerd 2.0 - 2.3 | CRI-O |
+============================+========================+================+
| Ubuntu 26.04 LTS | Yes | -- |
+----------------------------+------------------------+----------------+
Expand Down
Loading