openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

BZ1960736: Added warning to not create NetNamespace objects

Browse Source
This commit is contained in:
Christopher Tauchen
2021-05-19 12:20:56 +01:00
committed by openshift-cherrypick-robot
parent 4fbcb08dcf
commit 45e71d3f08
2 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
modules/nw-egress-ips-automatic.adoc
View File

@@ -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:
+

9
modules/nw-egress-ips-static.adoc
View File

@@ -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