From 2f770133d515d58a9fbbc7d8d05723cafdacc773 Mon Sep 17 00:00:00 2001 From: Sebastian Kopacz Date: Tue, 25 Oct 2022 14:44:27 -0400 Subject: [PATCH] OCP-2454: changing egress IP assignment desc --- modules/nw-egress-ips-about.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/nw-egress-ips-about.adoc b/modules/nw-egress-ips-about.adoc index a3d37fe7d6..a87544c7f4 100644 --- a/modules/nw-egress-ips-about.adoc +++ b/modules/nw-egress-ips-about.adoc @@ -179,7 +179,7 @@ When creating an `EgressIP` object, the following conditions apply to nodes that When a pod matches the selector for multiple `EgressIP` objects, there is no guarantee which of the egress IP addresses that are specified in the `EgressIP` objects is assigned as the egress IP address for the pod. -Additionally, if an `EgressIP` object specifies multiple egress IP addresses, there is no guarantee which of the egress IP addresses might be assigned to a pod. For example, if a pod matches a selector for an `EgressIP` object with two egress IP addresses, `10.10.20.1` and `10.10.20.2`, either might be assigned to the pod. +Additionally, if an `EgressIP` object specifies multiple egress IP addresses, there is no guarantee which of the egress IP addresses might be used. For example, if a pod matches a selector for an `EgressIP` object with two egress IP addresses, `10.10.20.1` and `10.10.20.2`, either might be used for each TCP connection or UDP conversation. [id="nw-egress-ips-node-architecture_{context}"] == Architectural diagram of an egress IP address configuration