add drivers 570.158.01 (#211)

* add drivers 570.158.01

Signed-off-by: Abigail McCarthy <[email protected]>

* fix typos

Signed-off-by: Abigail McCarthy <[email protected]>

---------

Signed-off-by: Abigail McCarthy <[email protected]>

Author: a-mccarthy

gpu-operator/gpu-operator-mig.rst

@@ -99,7 +99,7 @@ Perform the following steps to install the Operator and configure MIG:
 
    .. note::
 
-      Known Issue: For drivers 570.124.06, 570.133.20, and 570.148.08, 
+      Known Issue: For drivers 570.124.06, 570.133.20, 570.148.08, and 570.158.01,
       GPU workloads cannot be scheduled on nodes that have a mix of MIG slices and full GPUs. 
       This manifests as GPU pods getting stuck indefinitely in the ``Pending`` state. 
       It's recommended that you downgrade the driver to version 570.86.15 to work around this issue.

gpu-operator/life-cycle-policy.rst

@@ -92,9 +92,10 @@ Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.
 
    * - NVIDIA GPU Driver |ki|_
      - | `575.57.08 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-575-57-08/index.html>`_ 
-       | `570.148.08 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-570-148-08/index.html>`_ (default, recommended)
+       | `570.158.01 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-570-158-01/index.html>`_ (recommended)
+       | `570.148.08 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-570-148-08/index.html>`_ (default)
        | `550.163.01 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-550-163-01/index.html>`_
-       | `535.247.01 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-247-01/index.html>`_
+       | `535.247.01 <https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-247-01/index.html>`_ 
 
    * - NVIDIA Driver Manager for Kubernetes
      - `v0.8.0 <https://ngc.nvidia.com/catalog/containers/nvidia:cloud-native:k8s-driver-manager>`__
@@ -146,7 +147,7 @@ Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information.
 .. _known-issue:
 
    :sup:`1`
-   Known Issue: For drivers 570.124.06, 570.133.20, and 570.148.08, 
+   Known Issue: For drivers 570.124.06, 570.133.20, 570.148.08, and 570.158.01,
    GPU workloads cannot be scheduled on nodes that have a mix of MIG slices and full GPUs. 
    This manifests as GPU pods getting stuck indefinitely in the ``Pending`` state. 
    It's recommended that you downgrade the driver to version 570.86.15 to work around this issue.

gpu-operator/release-notes.rst

@@ -74,7 +74,7 @@ New Features
 Known Issues
 ------------
 
-* For drivers 570.124.06, 570.133.20, and 570.148.08, 
+* For drivers 570.124.06, 570.133.20, 570.148.08, and 570.158.01,
   GPU workloads cannot be scheduled on nodes that have a mix of MIG slices and full GPUs. 
   This manifests as GPU pods getting stuck indefinitely in the ``Pending`` state. 
   It's recommended that you downgrade the driver to version 570.86.15 to work around this issue.

gpu-operator/troubleshooting.rst

@@ -27,7 +27,7 @@ Pods stuck in Pending state in mixed MIG + full GPU environments
 .. rubric:: Issue
    :class: h4
 
-For drivers 570.124.06, 570.133.20, and 570.148.08, 
+For drivers 570.124.06, 570.133.20, 570.148.08, and 570.158.01,
 GPU workloads cannot be scheduled on nodes that have a mix of MIG slices and full GPUs.
 For more detailed information, see GitHub issue https://github.com/NVIDIA/gpu-operator/issues/1361.