Conversation
Documentation preview |
a-mccarthy
force-pushed
the
dev-26.3.0
branch
from
319d6c0 to
a4293b1
Compare
| You must uninstall an existing installation and then install the Operator again. | ||
| Uninstalling the Operator interrupts services and applications that require access to NVIDIA GPUs. |
There was a problem hiding this comment.
| You must uninstall an existing installation and then install the Operator again. | |
| Uninstalling the Operator interrupts services and applications that require access to NVIDIA GPUs. |
|
|
||
| #. Create a file, such as ``nvd-precomiled-some.yaml``, with contents like the following: | ||
|
|
||
| .. literalinclude:: ./manifests/input/nvd-precompiled-some.yaml |
There was a problem hiding this comment.
can we also change the driver version specified in these files?
| @@ -397,4 +393,4 @@ | |||
| .. code-block:: console | ||
|
|
||
| $ kubectl patch nvidiadriver/demo-silver --type='json' \ | ||
| -p='[{"op": "replace", "path": "/spec/version", "value": "525.125.06"}]' |
There was a problem hiding this comment.
Lets use updated version here.
a-mccarthy
force-pushed
the
dev-26.3.0
branch
3 times, most recently
from
3c58318 to
7003594
Compare
cdesiniotis
left a comment
cdesiniotis
left a comment
There was a problem hiding this comment.
Made a first pass. Will review again tomorrow.
gpu-operator/release-notes.rst
Outdated
| * Added full support for the NVIDIA Driver Custom Resource Definition (CRD). | ||
| Previously available in Technology Preview, the NVIDIA Driver CRD is now generally available. | ||
| Use this feature to configure multiple driver types and versions on different nodes or multiple operating system versions on nodes. | ||
| Refer to the :doc:`NVIDIA Driver Custom Resource Definition documentation <gpu-driver-configuration>` for more information. |
There was a problem hiding this comment.
Question -- do we want to call out the limitations regarding migration here?
|
|
||
| * Added support for KubeVirt GPU passthrough with Ubuntu 24.04 LTS and the VFIO framework. | ||
|
|
||
| * Added support for vGPU precompiled driver container for Azure Linux. |
There was a problem hiding this comment.
@rajathagasthya were we actually planning to call this out in the release notes? My gut says no...
gpu-operator/release-notes.rst
Outdated
| * Added PodSecurityContext support for DaemonSets (`PR #2120 <https://github.com/NVIDIA/gpu-operator/pull/2120>`_). | ||
| In ClusterPolicy, set ``spec.daemonsets.podSecurityContext``; in NVIDIADriver, set ``spec.podSecurityContext``. | ||
|
|
||
| * See `PR #2014 <https://github.com/NVIDIA/gpu-operator/pull/2014>`_ for related changes. |
There was a problem hiding this comment.
This bullet lacks context / feels out of place. Was this meant to be a sub-bullet for another bullet?
gpu-operator/release-notes.rst
Outdated
| * Improved the NVIDIA Kubernetes Device Plugin to avoid unnecessary GPU unbind/rebind operations during rolling updates of the vfio-manager DaemonSet. | ||
| This improves the stability of GPU passthrough workloads (KubeVirt, Kata Containers). | ||
| * Improved the Upgrade Controller to decrease unnecessary reconciliation in environments with Node Feature Discovery (NFD) enabled. | ||
| * Improved performance (`PR #2113 <https://github.com/NVIDIA/gpu-operator/pull/2113>`_). |
There was a problem hiding this comment.
What perf improvements? We should be more specific.
A suggestion (but someone might have a better suggestion 😄 ):
| * Improved performance (`PR #2113 <https://github.com/NVIDIA/gpu-operator/pull/2113>`_). | |
| * Improved performance of the clusterpolicy controller by reducing the number of API calls made (`PR #2113 <https://github.com/NVIDIA/gpu-operator/pull/2113>`_). |
There was a problem hiding this comment.
i updated this bullet, let me know if it make sense
|
|
||
| * Marked unused field ``defaultRuntime`` as optional in the ClusterPolicy. (`PR #2000 <https://github.com/NVIDIA/gpu-operator/pull/2000>`_) | ||
| * The NVIDIA Kata Manager for Kubernetes is now deprecated. | ||
| To enable Kata Containers for GPUs, install the upstream kata-deploy Helm chart, which deploys all Kata runtime classes, including the NVIDIA-specific runtime classes. |
There was a problem hiding this comment.
Should we link to the kata procedure (which you are adding in #365) here?
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com> Co-authored-by: Rajath Agasthya <rajathagasthya@gmail.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
| When post-release testing confirms support for newer versions of operands, these updates are identified as *recommended updates* to a GPU Operator version. | ||
| Refer to :ref:`Upgrading the NVIDIA GPU Operator` for more information. | ||
|
|
||
| .. note:: |
There was a problem hiding this comment.
@cdesiniotis is this accurate? In this release i feel like we can remove the separate components table in the gov-ready page, https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/install-gpu-operator-gov-ready.html#supported-gpu-operator-components. What components are still not gov ready? I want to make sure i note them correctly here.
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
5 participants
No description provided.