Merge pull request #56369 from Amrita42/BZ2061349

Author: adellape

modules/nw-sriov-configuring-operator.adoc

@@ -109,6 +109,10 @@ Admission Controller application. It provides the following capabilities:
 * Mutation of the `SriovNetworkNodePolicy` CR by setting the default value for the `priority` and `deviceType` fields when the CR is created or updated.
 
 By default the SR-IOV Network Operator Admission Controller webhook is enabled by the Operator and runs as a daemon set on all control plane nodes.
+
+NOTE: Use caution when disabling the SR-IOV Network Operator Admission Controller webhook. You can disable the webhook under specific circumstances, such as troubleshooting, or if you want to use unsupported devices.
+
+
 The following is an example of the Operator Admission Controller webhook pods running in a cluster with three control plane nodes:
 
 [source,terminal]
@@ -302,4 +306,3 @@ spec:
   disableDrain: true
 ----
 ====
-

networking/hardware_networks/about-sriov.adoc

@@ -68,6 +68,7 @@ A CNI plugin that attaches InfiniBand (IB) VF interfaces allocated from the SR-I
 [NOTE]
 ====
 The SR-IOV Network resources injector and SR-IOV Network Operator webhook are enabled by default and can be disabled by editing the `default` `SriovOperatorConfig` CR.
+Use caution when disabling the SR-IOV Network Operator Admission Controller webhook. You can disable the webhook under specific circumstances, such as troubleshooting, or if you want to use unsupported devices.
 ====
 
 include::modules/nw-sriov-supported-platforms.adoc[leveloffset=+2]