OCPBUGS-37272:updates example for pod connectivity check

Author: JoeAldinger

modules/nw-pod-network-connectivity-implementation.adoc

@@ -29,11 +29,24 @@ metadata:
 spec:
   # ...
     networkDiagnostics: <1>
-      mode: "" <2>
-      sourcePlacement: {} <3>
-      targetPlacement: {} <4>
+      mode: "All" <2>
+      sourcePlacement: <3>
+        nodeSelector:
+          checkNodes: groupA
+        tolerations:
+        - key: myTaint
+          effect: NoSchedule
+          operator: Exists
+      targetPlacement: <4>
+        nodeSelector:
+          checkNodes: groupB
+        tolerations:
+        - key: myOtherTaint
+          effect: NoExecute
+          operator: Exists
 ----
 <1> Specifies the network diagnostics configuration. If a value is not specified or an empty object is specified, and `spec.disableNetworkDiagnostics=true` is set in the `network.operator.openshift.io` custom resource named `cluster`, network diagnostics are disabled. If set, this value overrides `spec.disableNetworkDiagnostics=true`.
 <2> Specifies the diagnostics mode. The value can be the empty string, `All`, or `Disabled`. The empty string is equivalent to specifying `All`.
-<3> Optional: Specifies a selector for connectivity check source pods.
+<3> Optional: Specifies a selector for connectivity check source pods. You can use the `nodeSelector` and `tolerations` fields to further specify the `sourceNode` pods. You do not have to use both `nodeSelector` and `tolerations`, however, for both the source and target pods. These are optional fields that can be omitted.
 <4> Optional: Specifies a selector for connectivity check target pods.
+You can use the `nodeSelector` and `tolerations` fields to further specify the `targetNode` pods. You do not have to use both `nodeSelector` and `tolerations`, however, for both the source and target pods. These are optional fields that can be omitted.