From 857fbecf630cee2ec42ad3f1e2e52e921e7062f7 Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Mon, 26 Oct 2020 13:45:52 -0400 Subject: [PATCH] Clarify OVN-Kubernetes egress IP address platform support - https://bugzilla.redhat.com/show_bug.cgi?id=1891515 --- modules/nw-egress-ips-about.adoc | 22 +++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/modules/nw-egress-ips-about.adoc b/modules/nw-egress-ips-about.adoc index f5fa057b3125..20432987152a 100644 --- a/modules/nw-egress-ips-about.adoc +++ b/modules/nw-egress-ips-about.adoc @@ -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