diff --git a/docs/getting-started-kubernetes.rst b/docs/getting-started-kubernetes.rst index 3bf79844..4fbd2172 100644 --- a/docs/getting-started-kubernetes.rst +++ b/docs/getting-started-kubernetes.rst @@ -2559,8 +2559,6 @@ Configure NIC Firmware using the NIC Configuration Operator =========================================================================== `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:: `Maintenance Operator `_ is required to be deployed in the cluster for the NIC Configuration Operator - .. warning:: NVIDIA NIC Configuration Operator does not support FW reset flow for DPU mode. Check `limitations `_ .. note:: @@ -2568,7 +2566,14 @@ Configure NIC Firmware using the NIC Configuration Operator To set up a persistent NFS storage in the cluster, the `example from the CSI NFS Driver repository `_ might be used. After deploying the NFS server and NFS CSI driver, the `storage class `_ should become available in the cluster. The name of the storage class should then be passed when configuring the NIC Configuration Operator. -First install the Network Operator and deploy a NIC Cluster Policy CRD with NIC Configuration Operator enabled: +First install the Network Operator helm chart with the Maintenance Operator enabled and deploy a NIC Cluster Policy CRD with NIC Configuration Operator enabled: + +``values.yaml``: + +.. code-block:: yaml + + maintenanceOperator: + enabled: true ``nicclusterpolicy.yaml``: