Skip to content

Commit 8ccbb77

Browse files
committed
OCPBUGS-62278: Updated the Platform support table for EgressIp addresses
1 parent fc7b324 commit 8ccbb77

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

modules/nw-egress-ips-about.adoc

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,15 @@ ifeval::["{context}" == "configuring-egress-ips-ovn"]
66
:ovn:
77
endif::[]
88

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

12-
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.
13+
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.
1314

1415
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.
1516
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.
1617

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

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

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

4141
[cols="1,1",options="header"]
4242
|===
43-
4443
| Platform | Supported
4544

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

57+
The Egress IP address feature that runs on a secondary host network is supported on the following platform:
58+
59+
[cols="1,1",options="header"]
60+
|===
61+
| Platform | Supported
62+
63+
| Bare metal | Yes
5764
|===
5865
endif::openshift-rosa[]
5966

0 commit comments

Comments
 (0)