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

Merge pull request #104963 from openshift-cherrypick-robot/cherry-pick-104446-to-enterprise-4.21

Browse Source 
[enterprise-4.21] OSDOCS-17573: Added cluster-wide egress IP considerations
This commit is contained in:
Darragh Fitzmaurice
2026-01-19 15:34:04 +00:00
committed by GitHub
parent 471c7715c5 47c8abb9b0
commit ccac00fec5
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
modules/nw-egress-ips-object.adoc
View File

@@ -6,8 +6,21 @@
[id="nw-egress-ips-object_{context}"]
= EgressIP object
[role="_abstract"]
View the following YAML files to better understand how you can effectively configure an `EgressIP` object to better meet your needs.
When the `EgressIP` namespace selector matches the label on multiple namespaces, consider the following behaviors:
* All traffic for selected pods must pass through a single node. During times of high traffic, the network interface of the node might experience performance issues.
* An error in a label selector might change the outbound IP address for many cluster namespaces.
* Only a cluster administrator can create or change cluster-scoped objects.
* Packets must move from a pod that exists in a node to the named host node that is referenced in the `EgressIP` object. This approach adds a network hop.
[IMPORTANT]
====
Do not create egress rules, such as a single label selector, that forces all namespaces that exist in a cluster to use the same outbound IP address. This configuration can cause the node that hosts the IP address to crash during times of high network traffic.
====
The following YAML describes the API for the `EgressIP` object. The scope of the object is cluster-wide and is not created in a namespace.
[source,yaml]