OCPBUGS-42326: Added ETP=Local note to configuration-externalip.adoc

Author: dfitzmau

modules/configuration-externalip.adoc

@@ -26,9 +26,8 @@ As a cluster administrator, you must configure routing to externalIPs. You must
 To use IP address blocks defined by `autoAssignCIDRs` in {product-title}, you must configure the necessary IP address assignment and routing for your host network.
 ====
 
-The following YAML describes a service with an external IP address configured:
+The following YAML shows a `Service` object with a configured external IP:
 
-.Example `Service` object with `spec.externalIPs[]` set
 [source,yaml]
 ----
 apiVersion: v1

modules/nw-egress-ips-object.adoc

@@ -2,11 +2,17 @@
 //
 // * networking/ovn_kubernetes_network_provider/assigning-egress-ips-ovn.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nw-egress-ips-object_{context}"]
 = EgressIP object
 
 The following YAML describes the API for the `EgressIP` object. The scope of the object is cluster-wide; it is not created in a namespace.
 
+[IMPORTANT]
+====
+EgressIP selected pods cannot serve as backends for services with `externalTrafficPolicy` set to `Local`. If you try this configuration, service ingress traffic that targets the pods gets incorrectly rerouted to the egress node that hosts the EgressIP. This situation negatively impacts the handling of incoming service traffic and causes connections to drop. This leads to unavailable and non-functional services.
+====
+
 [source,yaml]
 ----
 apiVersion: k8s.ovn.org/v1
@@ -22,11 +28,8 @@ spec:
     ...
 ----
 <1> The name for the `EgressIPs` object.
-
 <2> An array of one or more IP addresses.
-
 <3> One or more selectors for the namespaces to associate the egress IP addresses with.
-
 <4> Optional: One or more selectors for pods in the specified namespaces to associate egress IP addresses with. Applying these selectors allows for the selection of a subset of pods within a namespace.
 
 The following YAML describes the stanza for the namespace selector: