diff --git a/docs/nic-conf-operator/nic-fw-configuration.rst b/docs/nic-conf-operator/nic-fw-configuration.rst index 9a8ac58e..98fae516 100644 --- a/docs/nic-conf-operator/nic-fw-configuration.rst +++ b/docs/nic-conf-operator/nic-fw-configuration.rst @@ -28,7 +28,12 @@ NIC Firmware Configuration :backlinks: none `NVIDIA NIC Configuration Operator `_ provides Kubernetes API (Custom Resource Definition) to allow Firmware update and configuration on NVIDIA NICs in a coordinated manner. It deploys a configuration daemon on each of the desired nodes to configure NVIDIA NICs there. NVIDIA NIC Configuration Operator uses `Maintenance Operator `_ to prepare a node for maintenance before the actual configuration. -.. warning:: NVIDIA NIC Configuration Operator does not support FW reset flow for DPU mode. Check :doc:`limitations <../release-notes>`. + +.. warning:: + NVIDIA NIC Configuration Operator does not support FW reset flow for DPU mode. Check :doc:`limitations <../release-notes>`. + +.. warning:: + NVIDIA Networking NIC Configuration Operator doesn't support Socket Direct Adapters. For more information about the CRD API, refer to :doc:`CRD API Reference `. diff --git a/docs/release-notes.rst b/docs/release-notes.rst index e9d64371..63e4768b 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -225,6 +225,8 @@ Known Limitations * - Version - Description + * - 25.10.0 + - | - NVIDIA Networking NIC Configuration Operator doesn't support Socket Direct Adapters. * - 25.7.0 - | - NVIDIA DOCA-OFED Driver container can not start after kernel upgrade on OCP. To make Driver container work, please remove `/var/opt/mofed-container/inventory` directory on the host. | - DOCA driver container deployment may fail if NVIDIA drivers are in use by third-party kernel modules or user-space applications. The recommended workaround is to use non-containerized DOCA drivers deployed via the DOCA-Host package.