anchor.diff:  
   By default, the manifest applies to all nodes in the cluster. To add the interface to specific nodes, add the `spec: nodeSelector` parameter and the appropriate `<key>:<value>` for your node selector.
   
  +You can configure multiple nmstate-enabled nodes concurrently. The configuration applies to 50% of the nodes in parallel. This strategy prevents the entire cluster from being unavailable if the network connection fails. To apply the policy configuration in parallel to a specific portion of the cluster, use the `maxUnavailable` field.
  +
   .Procedure
   
   . Create the `NodeNetworkConfigurationPolicy` manifest. The following example configures a Linux bridge on all worker nodes:
  
positive.code: apiVersion: nmstate.io/v1
  kind: NodeNetworkConfigurationPolicy
  metadata:
    name: <br1-eth1-policy> <1>
  spec:
    nodeSelector: <2>
      node-role.kubernetes.io/worker: "" <3>
    desiredState:
      interfaces:
        - name: br1
          description: Linux bridge with eth1 as a port <4>
          type: linux-bridge
          state: up
          ipv4:
  
negative.code: <1> Name of the policy.
  <2> Optional: If you do not include the `nodeSelector` parameter, the policy applies to all nodes in the cluster.
  <3> This example uses the `node-role.kubernetes.io/worker: ""` node selector to select all worker nodes in the cluster.
  <4> Optional: Specifies the maximum number of nmstate-enabled nodes that the policy configuration can be applied to concurrently. This parameter can be set to either a percentage value (string), for example, `"10%"`, or an absolute value (number), such as `3`.
  <5> Optional: Human-readable description for the interface.
  
  . Create the node network policy:
  +
  [source,terminal]
  ----
  $ oc apply -f br1-eth1_policy.yaml <1>
  ----
  <1> File name of the node network configuration policy manifest.
  +
  .Example output
  [source,terminal]
  ----
  NAME                     STATUS
  node01.br1-eth1-policy   Pending
  node02.br1-eth1-policy   Progressing
  node03.br1-eth1-policy   Available
  node04.br1-eth1-policy   Progressing
  node05.br1-eth1-policy   Progressing
  node06.br1-eth1-policy   Pending
  ----
  