Conditionalize egressip note - RHOSP

Resolves OSDOCS-5263

Author: maxwelldb

modules/nw-egress-ips-about.adoc

@@ -78,10 +78,12 @@ The annotation value is an array with a single object with fields that provide t
 
 Automatic attachment and detachment of egress IP addresses for traffic between nodes are available. This allows for traffic from many pods in namespaces to have a consistent source IP address to locations outside of the cluster. This also supports OpenShift SDN and OVN-Kubernetes, which is the default networking plugin in Red Hat OpenShift Networking in {product-title} {product-version}.
 
+ifdef::openshift-sdn[]
 [NOTE]
 ====
 The {rh-openstack} egress IP address feature creates a Neutron reservation port called `egressip-<IP address>`. Using the same {rh-openstack} user as the one used for the {product-title} cluster installation, you can assign a floating IP address to this reservation port to have a predictable SNAT address for egress traffic. When an egress IP address on an {rh-openstack} network is moved from one node to another, because of a node failover, for example, the Neutron reservation port is removed and recreated. This means that the floating IP association is lost and you need to manually reassign the floating IP address to the new reservation port.
 ====
+endif::openshift-sdn[]
 
 The following examples illustrate the annotation from nodes on several public cloud providers. The annotations are indented for readability.