Updated array with - key for pods nodes 51826

 Added affinity rules to pod limitation

Author: obrown1205

modules/nw-metallb-operator-limit-speaker-to-nodes.adoc

@@ -26,7 +26,7 @@ spec:
   nodeSelector:  <.>
     node-role.kubernetes.io/worker: ""
   speakerTolerations:   <.>
-    key: "Example"
+  - key: "Example"
     operator: "Exists"
     effect: "NoExecute"
 ----
@@ -36,4 +36,4 @@ spec:
 After you apply a manifest with the `spec.nodeSelector` field, you can check the number of pods that the Operator deployed with the `oc get daemonset -n metallb-system speaker` command.
 Similarly, you can display the nodes that match your labels with a command like `oc get nodes -l node-role.kubernetes.io/worker=`.
 
-You can optionally allow the node to control which speaker pods should, or should not, be scheduled on them by applying a list of tolerations. For more information about taints and tolerations, see the additional resources.
+You can optionally allow the node to control which speaker pods should, or should not, be scheduled on them by using affinity rules. You can also limit these pods by applying a list of tolerations. For more information about affinity rules, taints, and tolerations, see the additional resources.