Updates egress ip docs to provide proper command for return egess ip addresses

Author: Steven Smith

modules/nw-egress-ips-assign.adoc

@@ -49,11 +49,38 @@ $ oc apply -f <egressips_name>.yaml <1>
 egressips.k8s.ovn.org/<egressips_name> created
 ----
 
-. Optional: Save the `<egressips_name>.yaml` file so that you can make changes later.
+. Optional: Store the `<egressips_name>.yaml` file so that you can make changes later.
+
 . Add labels to the namespace that requires egress IP addresses. To add a label to the namespace of an `EgressIP` object defined in step 1, run the following command:
 +
 [source,terminal]
 ----
 $ oc label ns <namespace> env=qa <1>
 ----
 <1> Replace `<namespace>` with the namespace that requires egress IP addresses.
+
+.Verification
+
+* To show all egress IPs that are in use in your cluster, enter the following command:
++
+[source,terminal]
+----
+$ oc get egressip -o yaml
+----
++
+[NOTE]
+====
+The command `oc get egressip` only returns one egress IP address regardless of how many are configured. This is not a bug and is a limitation of Kubernetes. As a workaround, you can pass in the `-o yaml` or `-o json` flags to return all egress IPs addresses in use.
+====
++
+.Example output
++
+[source,terminal]
+----
+# ...
+spec:
+  egressIPs:
+  - 192.168.127.10
+  - 192.168.127.11
+# ...
+----