Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions gpu-operator/gpu-operator-rdma.rst
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ NVIDIA recommends using the DMA-BUF rather than using the ``nvidia-peermem`` ker

The Operator uses GDS driver version 2.17.5 or newer.
This version and higher is only supported with the NVIDIA Open GPU Kernel module driver.
In GPU Operator v25.3.0 and later, the ``driver.kernelModuleType`` default is ``auto``, for the supported driver versions.
This configuration allows the GPU Operator to choose the recommended driver kernel module type depending on the driver branch and the GPU devices available.
In GPU Operator v25.3.0 and later, the ``driver.kernelModuleType`` default is ``auto``, for the supported driver versions.
This configuration allows the GPU Operator to choose the recommended driver kernel module type depending on the driver branch and the GPU devices available.
Newer driver versions will use the open kernel module by default, however to make sure you are using the open kernel module, include ``--set driver.kernelModuleType=open`` command-line argument in your helm Operator install command.

In conjunction with the Network Operator, the GPU Operator can be used to
Expand Down
39 changes: 23 additions & 16 deletions gpu-operator/life-cycle-policy.rst
Original file line number Diff line number Diff line change
Expand Up @@ -88,10 +88,11 @@ Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.
:header-rows: 2

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

* - v26.7.0
- v26.7.1
- v26.7.2

* - NVIDIA GPU Driver
- | `610.57.04 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-610-57-04/index.html>`_
Expand All @@ -101,66 +102,72 @@ Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.
| `610.57.04 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-610-57-04/index.html>`_
| `595.91.07 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-595-91-07/index.html>`_ (**R**, **D**)
| `580.173.02 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-580-173-02/index.html>`_
- | `615.71.09 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-615-71-09/index.html>`_
| `610.57.04 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-610-57-04/index.html>`_
| `595.91.07 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-595-91-07/index.html>`_ (**R**, **D**)
| `580.173.02 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-580-173-02/index.html>`_

* - NVIDIA Driver Manager for Kubernetes
- `v0.12.0 <https://ngc.nvidia.com/catalog/containers/nvidia:cloud-native:k8s-driver-manager>`__
- `v0.12.1 <https://ngc.nvidia.com/catalog/containers/nvidia:cloud-native:k8s-driver-manager>`__
- :cspan:`1` `v0.12.1 <https://ngc.nvidia.com/catalog/containers/nvidia:cloud-native:k8s-driver-manager>`__

* - NVIDIA Container Toolkit
- `1.20.0 <https://github.com/NVIDIA/nvidia-container-toolkit/releases>`__
- `1.20.1 <https://github.com/NVIDIA/nvidia-container-toolkit/releases>`__
- :cspan:`1` `1.20.1 <https://github.com/NVIDIA/nvidia-container-toolkit/releases>`__

* - NVIDIA Device Plugin for Kubernetes
- `0.20.0 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__
- `0.20.1 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__
- :cspan:`1` `0.20.1 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__

* - DRA Driver for NVIDIA GPUs
- :cspan:`1` `v${dra_version} <https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/releases/tag/v${dra_version}>`__
- :cspan:`1` `v0.5.0 <https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/releases/tag/v0.5.0>`__

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.

Suggested change
- :cspan:`1` `v0.5.0 <https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/releases/tag/v0.5.0>`__
- :cspan:`1` `v0.5.1 <https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/releases/tag/v0.5.1>`__

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 thought that I had this one covered. v0.5.0 for 26.7.0 and 26.7.1, v0.5.1 for 26.7.2:

image

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.

Yes, this is correct. Nvm what I said then

- `v${dra_version} <https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/releases/tag/v${dra_version}>`__

* - DCGM Exporter
- `v4.6.0-4.8.3 <https://github.com/NVIDIA/dcgm-exporter/releases>`__
- `v4.6.1-4.8.4 <https://github.com/NVIDIA/dcgm-exporter/releases>`__
- :cspan:`1` `v4.6.1-4.8.4 <https://github.com/NVIDIA/dcgm-exporter/releases>`__

* - Node Feature Discovery
- :cspan:`1` `v0.19.0 <https://github.com/kubernetes-sigs/node-feature-discovery/releases/>`__
- :cspan:`2` `v0.19.0 <https://github.com/kubernetes-sigs/node-feature-discovery/releases/>`__

* - | NVIDIA GPU Feature Discovery
| for Kubernetes
- `0.20.0 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__
- `0.20.1 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__
- :cspan:`1` `0.20.1 <https://github.com/NVIDIA/k8s-device-plugin/releases>`__

* - NVIDIA MIG Manager for Kubernetes
- `0.15.0 <https://github.com/NVIDIA/mig-parted/blob/main/CHANGELOG.md>`__
- `0.15.1 <https://github.com/NVIDIA/mig-parted/blob/main/CHANGELOG.md>`__
- :cspan:`1` `0.15.1 <https://github.com/NVIDIA/mig-parted/blob/main/CHANGELOG.md>`__

* - DCGM
- `4.6.0-1 <https://docs.nvidia.com/datacenter/dcgm/latest/release-notes/changelog.html>`__
- `4.6.1-1 <https://docs.nvidia.com/datacenter/dcgm/latest/release-notes/changelog.html>`__
- :cspan:`1` `4.6.1-1 <https://docs.nvidia.com/datacenter/dcgm/latest/release-notes/changelog.html>`__

* - Validator for NVIDIA GPU Operator
- v26.7.0
- v26.7.1
- v26.7.2

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

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

* - NVIDIA GDS Driver |gds|_
- :cspan:`1` `2.29.4 <https://github.com/NVIDIA/gds-nvidia-fs/releases>`__
- :cspan:`2` `2.29.4 <https://github.com/NVIDIA/gds-nvidia-fs/releases>`__

* - | NVIDIA Confidential Computing
| Manager for Kubernetes
- `v0.4.3 <https://github.com/NVIDIA/k8s-cc-manager/releases>`__
- `v0.4.4 <https://github.com/NVIDIA/k8s-cc-manager/releases>`__
- :cspan:`1` `v0.4.4 <https://github.com/NVIDIA/k8s-cc-manager/releases>`__

* - NVIDIA GDRCopy Driver
- :cspan:`1` `v2.6 <https://github.com/NVIDIA/gdrcopy/releases>`__
- :cspan:`2` `v2.6 <https://github.com/NVIDIA/gdrcopy/releases>`__

* - NVIDIA Kata Sandbox Device Plugin
- :cspan:`1` `v0.0.5 <https://github.com/NVIDIA/sandbox-device-plugin/releases>`__
- :cspan:`2` `v0.0.5 <https://github.com/NVIDIA/sandbox-device-plugin/releases>`__

.. _gds-open-kernel:

Expand Down
4 changes: 2 additions & 2 deletions gpu-operator/nvidia-driver-configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -310,13 +310,13 @@ The following table describes some of the fields in the custom resource.
- None

* - ``default``
- Specifies whether the resource is the fallback driver configuration for GPU nodes that do not
- Optional. Specifies whether the resource is the fallback driver configuration for GPU nodes that do not
match a non-default resource.
Only one resource can be the default, and a default resource cannot specify ``nodeSelector``.
- ``false``

* - ``driverType``
- Specifies one of the following:
- Optional. Specifies one of the following:

- ``gpu`` to use the NVIDIA data-center GPU driver.
- ``vgpu`` to use the NVIDIA vGPU guest driver.
Expand Down
55 changes: 55 additions & 0 deletions gpu-operator/release-notes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,61 @@ Refer to the :ref:`GPU Operator Component Matrix` for a list of software compone

----

.. _v26.7.2:

26.7.2
======

New Features
------------

* Updated software component versions:

- DRA Driver for NVIDIA GPUs v0.5.1

Improvements
------------

* The NVIDIA DCGM and NVIDIA DCGM Exporter daemon sets, pods, and services now include the ``app.kubernetes.io/component`` label with the value ``nvidia-dcgm`` or ``nvidia-dcgm-exporter``.
The label applies to deployments managed by the ``ClusterPolicy`` resource and by the ``GPUCluster`` resource.
If you specify the ``app.kubernetes.io/component`` label in the ``daemonsets.labels`` field, the Operator does not apply your value to operands that already have the label, such as NVIDIA DCGM, NVIDIA DCGM Exporter, and the NVIDIA GPU Driver.
The Operator logs a message when it skips a conflicting value.
(`GPU Operator PR #3017 <https://github.com/NVIDIA/gpu-operator/pull/3017>`__)

Fixed Issues
------------

* Fixed an issue on Red Hat OpenShift Container Platform where workloads that request MPS sharing remained in the ``ContainerCreating`` state when you install the DRA Driver for NVIDIA GPUs with the ``GPUCluster`` resource and enable the ``MPSSupport`` feature gate.
The MPS control daemon now runs with the DRA driver service account, and the ``nvidia-dra-driver`` SCC now allows host PID access.
(`GPU Operator PR #3008 <https://github.com/NVIDIA/gpu-operator/pull/3008>`__)

* Fixed an issue on Red Hat OpenShift Container Platform where ComputeDomain daemon pods failed to start when you install the DRA Driver for NVIDIA GPUs with the ``GPUCluster`` resource and use ComputeDomains.
The ComputeDomain daemon service account can now use the ``anyuid`` SCC, and the ComputeDomain daemon role can now delete ``ComputeDomainClique`` resources.
(`GPU Operator PR #3011 <https://github.com/NVIDIA/gpu-operator/pull/3011>`__, `Issue #3010 <https://github.com/NVIDIA/gpu-operator/issues/3010>`__)

* Fixed an issue where changing a node label used in an ``NVIDIADriver`` node selector did not always reassign the node to the matching NVIDIA driver resource.
The Operator now reconciles driver ownership when any label in any NVIDIA driver node selector is added, changed, or removed.
(`GPU Operator PR #3003 <https://github.com/NVIDIA/gpu-operator/pull/3003>`__, `Issue #3004 <https://github.com/NVIDIA/gpu-operator/issues/3004>`__)

* Fixed an issue where the MPS control daemon did not reload after an MPS sharing configuration change.
The configuration manager now signals the ``mps-control-daemon`` process by the process name that the container starts.
(`GPU Operator PR #2974 <https://github.com/NVIDIA/gpu-operator/pull/2974>`__)

* Fixed an issue where the Operator could not update recurring Kubernetes events, such as ``GPUDriverUpgrade`` events.
The Operator cluster role now includes the ``patch`` verb for events.
(`GPU Operator PR #2995 <https://github.com/NVIDIA/gpu-operator/pull/2995>`__)

* Fixed an issue where OLM installations on Arm64 GPU nodes failed to start NVIDIA vGPU Device Manager with ``Exec format error``.
The OLM bundle now pins the multi-architecture image index digest for NVIDIA vGPU Device Manager v0.5.1.
(`GPU Operator PR #3013 <https://github.com/NVIDIA/gpu-operator/pull/3013>`__, `Issue #3012 <https://github.com/NVIDIA/gpu-operator/issues/3012>`__)

* Fixed an issue where Operator Lifecycle Manager (OLM) upgrades could fail with ``spec.default: Required value`` when validating existing ``NVIDIADriver`` resources.
The ``spec.default`` and ``spec.driverType`` fields are now optional, with defaults of ``false`` and ``gpu``, respectively.
(`GPU Operator PR #3046 <https://github.com/NVIDIA/gpu-operator/pull/3046>`__)


----

.. _v26.7.1:

26.7.1
Expand Down
21 changes: 10 additions & 11 deletions openshift/install-gpu-ocp.rst
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ As a cluster administrator, you can install the **NVIDIA GPU Operator** using th

subscription.operators.coreos.com/gpu-operator-certified created

#. Optional: Log in to the web console and navigate to the **Ecosystem** > **Installed Operators** and select **NVIDIA GPU Operator**.
#. Optional: Log in to the web console and navigate to the **Ecosystem** > **Installed Operators** and select **NVIDIA GPU Operator**.
In versions before 4.20, navigate to **Operators** > **Installed Operators** and select **NVIDIA GPU Operator**.

In the ``Project: nvidia-gpu-operator`` the following is displayed:
Expand Down Expand Up @@ -199,7 +199,7 @@ when using **NVIDIA vGPU**. Refer to the appropriate sections below.
.. _create-cluster-policy-web-console:

Create the cluster policy using the web console
-----------------------------------------------
===============================================

#. In the OpenShift Container Platform web console, from the side menu, select **Ecosystem** > **Installed Operators** (for versions before 4.20, look for **Operators** > **Installed Operators**), and click **NVIDIA GPU Operator**.

Expand All @@ -224,14 +224,13 @@ Create the cluster policy using the web console
.. _verify-gpu-operator-install-ocp:

Create the cluster policy using the CLI
---------------------------------------

=======================================

#. Create the ClusterPolicy:

.. code-block:: console

$ oc get csv -n nvidia-gpu-operator $STARTING_CSV -o jsonpath='{.metadata.annotations.alm-examples}' | jq -r 'map(select(.kind == "ClusterPolicy")) | .[0]' > clusterpolicy.json
$ oc get csv -n nvidia-gpu-operator $STARTING_CSV -o jsonpath='{.metadata.annotations.alm-examples}' | jq -r 'map(select(.kind == "ClusterPolicy")) | .[0]' > clusterpolicy.json

.. note:: $STARTING_CSV is the value of the ``startingCSV`` field in the ``Subscription`` CR sample created in the :ref:`install-gpu-ocp` section.

Expand All @@ -258,7 +257,7 @@ Create the ClusterPolicy instance with NVIDIA vGPU
***************************************************************************

Prerequisites
--------------
==============

Before creating the ClusterPolicy for NVIDIA vGPU, ensure the following:

Expand Down Expand Up @@ -288,16 +287,16 @@ Before creating the ClusterPolicy for NVIDIA vGPU, ensure the following:
-n nvidia-gpu-operator

Create the cluster policy using the web console
-----------------------------------------------
===============================================

#. In the OpenShift Container Platform web console, from the side menu, select **Ecosystem** > **Installed Operators** and select **NVIDIA GPU Operator**.
In versions before 4.20, navigate to **Operators** > **Installed Operators** and select **NVIDIA GPU Operator**.

#. Select the **ClusterPolicy** tab, then click **Create ClusterPolicy**. The platform assigns the default name *gpu-cluster-policy*.

#. Under the **NVIDIA GPU/vGPU Driver config** section fill in the following information
* Specify the ``secretName`` as the name of the licensing ``Secret`` created during the prerequisite steps for NVIDIA vGPU (for example, ``licensing-config``).

* Specify the ``secretName`` as the name of the licensing ``Secret`` created during the prerequisite steps for NVIDIA vGPU (for example, ``licensing-config``).

.. note::

Expand All @@ -319,13 +318,13 @@ Create the cluster policy using the web console


Create the cluster policy using the CLI
---------------------------------------
=======================================

#. Create the ClusterPolicy:

.. code-block:: console

$ oc get csv -n nvidia-gpu-operator $STARTING_CSV -o jsonpath='{.metadata.annotations.alm-examples}' | jq -r 'map(select(.kind == "ClusterPolicy")) | .[0]') > clusterpolicy.json
$ oc get csv -n nvidia-gpu-operator $STARTING_CSV -o jsonpath='{.metadata.annotations.alm-examples}' | jq -r 'map(select(.kind == "ClusterPolicy")) | .[0]') > clusterpolicy.json

.. note:: $STARTING_CSV is the value of the ``startingCSV`` field in the ``Subscription`` CR sample created in the :ref:`install-gpu-ocp` section.

Expand Down
2 changes: 1 addition & 1 deletion repo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ docs_root = "${root}/gpu-operator"
project = "gpu-operator"
name = "NVIDIA GPU Operator"
version = "26.7" # Update repo_docs.projects.openshift.version to match latest patch version maj.min.patch
source_substitutions = { minor_version = "26.7", version = "v26.7.1", recommended = "595.91.07", dra_version = "0.5.0", kata_version = "4.0.0" }
source_substitutions = { minor_version = "26.7", version = "v26.7.2", recommended = "595.91.07", dra_version = "0.5.1", kata_version = "4.0.0" }
copyright_start = 2020
sphinx_exclude_patterns = [
"life-cycle-policy.rst",
Expand Down
Loading