anchor.diff:  . Update the default SriovOperatorConfig Custom Resource
   +
   ----
  -oc patch sriovoperatorconfig default --patch '[{"op": "replace", "path": "/spec/configDaemonNodeSelector", "value": {<node-label>}}]' --type=json
  +$ oc patch sriovoperatorconfig default --patch '[{"op": "replace", "path": "/spec/configDaemonNodeSelector", "value": {<node-label>}}]' --type=json -n openshift-sriov-network-operator
   ----
  +
  +[NOTE]
  +=====
  +Replace `<node-label>` with label to apply.
  +For example: `node-role.kubernetes.io/worker: ""`.
  +=====
  +
  +[NOTE]
  +=====
  +Updating of `configDaemonNodeSelector` will cause `SR-IOV Network Config Daemon`
  +be recreated on all the nodes that have `SR-IOV Network Config Daemon` deployed.
  +This will block user from applying new SR-IOV Network Node Policy and creating
  +new SR-IOV pods until `SR-IOV Network Config Daemon` is recreated on target nodes.
  +=====
  
positive.code: . Update the default SriovOperatorConfig Custom Resource
  +
  ----
  oc patch sriovoperatorconfig default --patch '{ "spec": { "enableOperatorWebhook": false}}' --type=merge
  ----
  
  [id="configuring-custom-nodeselector_{context}"]
  == Configuring Custom NodeSelector for SRIOV Network Config Daemon
  
  The SR-IOV Network Config Daemon is in charge of discover and config the SRIOV
  network devices on the nodes.
  
  By default, it will be deployed to all the `worker` nodes in the cluster. You
  can follow this procedure to select the nodes, where the SR-IOV Network Config
  
negative.code: . Update the default SriovOperatorConfig Custom Resource
  +
  ----
  $ oc patch sriovoperatorconfig default --patch '{ "spec": { "enableInjector": false}}' --type=merge -n openshift-sriov-network-operator
  ----
  
  . To re-enable Network Resources Injector
  +
  ----
  $ oc patch sriovoperatorconfig default --patch '{ "spec": { "enableInjector": true}}' --type=merge -n openshift-sriov-network-operator
  ----
  
  [id="disabling-sr-iov-operator-admission-control-webhook_{context}"]
  == Disabling SR-IOV Operator admission controller webhook
  The SRIOV Operator Admission Controller Webhook is a Kubernetes Dynamic
  Admission Controller application that:
  
  * Validating the `SriovNetworkNodePolicy` Custom Resource when it being created
  or updated.
  * Mutating the `SriovNetworkNodePolicy` Custom Resource by setting the default
  value to `priority` and `deviceType` when it being created or updated.
  
  By default the SR-IOV Operator Admission Controller Webhook will be enabled by
  the operator and runs as a Kubernetes DaemonSet on all master nodes. Below is
  an example of Operator Admission Controller Webhook pods running in a cluster
  with three master nodes:
  
  ----
  $ oc get pods -n openshift-sriov-network-operator
  NAME                                      READY   STATUS    RESTARTS   AGE
  operator-webhook-9jkw6                    1/1     Running   0          16m
  operator-webhook-kbr5p                    1/1     Running   0          16m
  operator-webhook-rpfrl                    1/1     Running   0          16m
  ----
  
  Follow this procedure to disable it.
  
  .Prerequisites
  
  