Merge pull request #32639 from ctauchen/BZ#1960736

BZ1960736: Added warning to not create NetNamespace objects

Author: jeana-redhat

modules/nw-egress-ips-automatic.adoc

@@ -10,8 +10,8 @@ for a specific namespace across one or more nodes.
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Access to the cluster as a user with the `cluster-admin` role.
+* You have access to the cluster as a user with the `cluster-admin` role.
+* You have installed the OpenShift CLI (`oc`).
 
 .Procedure
 
@@ -46,6 +46,11 @@ $ oc patch netnamespace project2 --type=merge -p \
   '{"egressIPs": ["192.168.1.101"]}'
 ----
 +
+[NOTE]
+====
+Because OpenShift SDN manages the `NetNamespace` object, you can make changes only by modifying the existing `NetNamespace` object. Do not create a new `NetNamespace` object.
+====
+
 . Indicate which nodes can host egress IP addresses by setting the `egressCIDRs`
 parameter for each host using the following JSON:
 +

modules/nw-egress-ips-static.adoc

@@ -9,8 +9,8 @@ In {product-title} you can associate one or more egress IP addresses with a name
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Access to the cluster as a user with the `cluster-admin` role.
+* You have access to the cluster as a user with the `cluster-admin` role.
+* You have installed the OpenShift CLI (`oc`).
 
 .Procedure
 
@@ -43,6 +43,11 @@ $ oc patch netnamespace project1 --type=merge \
 ----
 +
 To provide high availability, set the `egressIPs` value to two or more IP addresses on different nodes. If multiple egress IP addresses are set, then pods use all egress IP addresses roughly equally.
++
+[NOTE]
+====
+Because OpenShift SDN manages the `NetNamespace` object, you can make changes only by modifying the existing `NetNamespace` object. Do not create a new `NetNamespace` object.
+====
 
 . Manually assign the egress IP to the node hosts. Set the `egressIPs` parameter
 on the `HostSubnet` object on the node host. Using the following JSON, include