Skip to content

OCPBUGS-62278: Updated the Platform support table for EgressIp addresses #100029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OCPBUGS-62278: Updated the Platform support table for EgressIp addresses #100029

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions modules/nw-egress-ips-about.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,15 @@ ifeval::["{context}" == "configuring-egress-ips-ovn"]
:ovn:
endif::[]

:_mod-docs-content-type: CONCEPT
[id="nw-egress-ips-about_{context}"]
= Egress IP address architectural design and implementation

The {product-title} egress IP address functionality allows you to ensure that the traffic from one or more pods in one or more namespaces has a consistent source IP address for services outside the cluster network.
By using the {product-title} egress IP address functionality, you can ensure that the traffic from one or more pods in one or more namespaces has a consistent source IP address for services outside the cluster network.

For example, you might have a pod that periodically queries a database that is hosted on a server outside of your cluster. To enforce access requirements for the server, a packet filtering device is configured to allow traffic only from specific IP addresses.
To ensure that you can reliably allow access to the server from only that specific pod, you can configure a specific egress IP address for the pod that makes the requests to the server.


An egress IP address assigned to a namespace is different from an egress router, which is used to send traffic to specific destinations.

ifndef::openshift-rosa[]
Expand All @@ -36,11 +36,10 @@ ifndef::openshift-rosa[]
[id="nw-egress-ips-platform-support_{context}"]
== Platform support

Support for the egress IP address functionality on various platforms is summarized in the following table:
The Egress IP address feature that runs on a primary host network is supported on the following platforms:

[cols="1,1",options="header"]
|===

| Platform | Supported

| Bare metal | Yes
Expand All @@ -53,7 +52,15 @@ Support for the egress IP address functionality on various platforms is summariz
| {ibm-z-name} and {ibm-linuxone-name} for {op-system-base-full} KVM | Yes
| {ibm-power-name} | Yes
| Nutanix | Yes
|===

The Egress IP address feature that runs on secondary host networks is supported on the following platform:

[cols="1,1",options="header"]
|===
| Platform | Supported

| Bare metal | Yes
|===
endif::openshift-rosa[]

Expand Down