Merge pull request #65075 from stevsmit/OCPBUGS-19477

Adds an IMPORTANT admonition to limitations of egress firewall

Author: stevsmit

modules/nw-egressnetworkpolicy-about.adoc

@@ -96,6 +96,13 @@ Egress firewall rules do not apply to traffic that goes through routers. Any use
 An egress firewall has the following limitations:
 
 * No project can have more than one {kind} object.
+ifdef::openshift-sdn[]
++
+[IMPORTANT]
+====
+The creation of more than one {kind} object is allowed, however it should not be done. When you create more than one {kind} object, the following message is returned: `dropping all rules`. In actuality, all external traffic is dropped, which can cause security risks for your organization.
+====
+endif::openshift-sdn[]
 
 ifdef::ovn[]
 * A maximum of one {kind} object with a maximum of 8,000 rules can be defined per project.
@@ -114,7 +121,7 @@ ifdef::openshift-sdn[]
   - Projects merged by using the `oc adm pod-network join-projects` command cannot use an egress firewall in any of the joined projects.
 endif::openshift-sdn[]
 
-Violating any of these restrictions results in a broken egress firewall for the project, and might cause all external network traffic to be dropped.
+Violating any of these restrictions results in a broken egress firewall for the project. Consequently, all external network traffic is dropped, which can cause security risks for your organization.
 
 An Egress Firewall resource can be created in the `kube-node-lease`, `kube-public`, `kube-system`, `openshift` and `openshift-` projects.