11.3. Configuring the SR-IOV Network Operator

• Mutation of resource requests and limits in Pod specification to add an SR-IOV resource name according to an SR-IOV network attachment definition annotation.
• Mutation of Pod specifications with downward API volume to expose pod annotations and labels to the running container as files under the /etc/podnetinfo path.

• Validation of the SriovNetworkNodePolicy CR when it is created or updated.
• Mutation of the SriovNetworkNodePolicy CR by setting the default value for the priority and deviceType fields when the CR is created or updated.

Prerequisites

• Install the OpenShift CLI (oc).
• Log in as a user with cluster-admin privileges.
• You must have installed the SR-IOV Operator.

Procedure

• Set the enableInjector field. Replace <value> with false to disable the feature or true to enable the feature.

  $ oc patch sriovoperatorconfig default \
    --type=merge -n openshift-sriov-network-operator \
    --patch '{ "spec": { "enableInjector": <value> } }'

Prerequisites

• Install the OpenShift CLI (oc).
• Log in as a user with cluster-admin privileges.
• You must have installed the SR-IOV Operator.

Procedure

• Set the enableOperatorWebhook field. Replace <value> with false to disable the feature or true to enable it:

  $ oc patch sriovoperatorconfig default --type=merge \
    -n openshift-sriov-network-operator \
    --patch '{ "spec": { "enableOperatorWebhook": <value> } }'

Procedure

• To update the node selector for the operator, enter the following command:

  $ oc patch sriovoperatorconfig default --type=json \
    -n openshift-sriov-network-operator \
    --patch '[{
        "op": "replace",
        "path": "/spec/configDaemonNodeSelector",
        "value": {<node-label>}
      }]'

  Replace <node-label> with a label to apply as in the following example: "node-role.kubernetes.io/worker": "".