anchor.diff:  ----
   $ oc get pod -n openshift-ingress
   
  -NAME                              READY     STATUS        RESTARTS   AGE       IP           NODE                           NOMINATED NODE
  -router-default-86798b4b5d-bdlvd   1/1       Running       0          28s       10.130.2.4   ip-10-0-217-226.ec2.internal   <none>
  -router-default-955d875f4-255g8    0/1       Terminating   0          19h       10.129.2.4   ip-10-0-148-172.ec2.internal   <none>
  +NAME                              READY     STATUS        RESTARTS   AGE
  +router-default-86798b4b5d-bdlvd   1/1       Running       0          28s
  +router-default-955d875f4-255g8    0/1       Terminating   0          19h
   ----
   +
   In this example, the running pod is on the `ip-10-0-217-226.ec2.internal` node.
  
positive.code: $ oc edit ingresscontroller default -n openshift-ingress-operator -o yaml
  ----
  +
  Update the `nodeSelector` stanza to reference the `infra` label as shown:
  +
  [source,yaml]
  ----
    nodeSelector:
      matchLabels:
        node-role.kubernetes.io/infra: ""
  ...
  ----
  
  . Confirm that the router pod is running on the `infra` node.
  
negative.code: . View the `IngressController` Custom Resource for the router Operator:
  +
  ----
  $ oc get ingresscontroller default -n openshift-ingress-operator -o yaml
  ----
  +
  The command output resembles the following text:
  +
  [source,yaml]
  ----
  apiVersion: operator.openshift.io/v1
  kind: IngressController
  metadata:
  