chore: Document Socket Direct Adapters limitations

Signed-off-by: Ivan Kolodiazhnyi <[email protected]>

Author: e0ne

docs/nic-conf-operator/nic-fw-configuration.rst

@@ -28,7 +28,12 @@ NIC Firmware Configuration
    :backlinks: none
 
 `NVIDIA NIC Configuration Operator <https://github.com/Mellanox/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 <https://github.com/Mellanox/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 <crds>`.
 

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.