Skip to content
Merged
Changes from all commits
Commits
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
22 changes: 15 additions & 7 deletions modules/nw-egress-ips-about.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -26,16 +26,24 @@ An egress IP address is implemented as an additional IP address on the primary n
[id="nw-egress-ips-platform-support_{context}"]
== Platform support

While you can use the egress IP address functionality on any platform that {product-title} supports, the following platform specific considerations apply:
Support for the egress IP address functionality on various platforms is summarized in the following table:

Cloud platforms::
Additional IP addresses must be assigned manually to appropriate nodes by an administrator.
[IMPORTANT]
====
The egress IP address implementation is not compatible with Amazon Web Services (AWS), Azure Cloud, or any other public cloud platform incompatible with the automatic layer 2 network manipulation required by the egress IP feature.
====

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

| Platform | Supported

{rhosp}::
Additional configuration by an administrator is necessary to allow {product-title} to automatically assign additional IP addresses to nodes.
| Bare metal | Yes
| vSphere | Yes
| {rhosp} | No
| Public cloud | No

vSphere::
Additional configuration by an administrator is necessary to allow {product-title} to automatically assign additional IP addresses to nodes.
|===

[id="nw-egress-ips-considerations_{context}"]
== Assignment of egress IPs to pods
Expand Down