Merge pull request #57579 from kquinn1204/TELCODOCS-1120

TELCODOCS-1120 removing section on incompatibility with IP failover

Author: kelbrown20

modules/nw-metallb-when-metallb.adoc

@@ -12,3 +12,8 @@ You must configure your networking infrastructure to ensure that network traffic
 
 After deploying MetalLB with the MetalLB Operator, when you add a service of type `LoadBalancer`, MetalLB provides a platform-native load balancer.
 
+MetalLB operating in layer2 mode provides support for failover by utilizing a mechanism similar to IP failover. However, instead of relying on the virtual router redundancy protocol (VRRP) and keepalived, MetalLB leverages a gossip-based protocol to identify instances of node failure. When a failover is detected, another node assumes the role of the leader node, and a gratuitous ARP message is dispatched to broadcast this change.
+
+MetalLB operating in layer3 or border gateway protocol (BGP) mode delegates failure detection to the network. The BGP router or routers that the {product-title} nodes have established a connection with will identify any node failure and terminate the routes to that node.
+
+Using MetalLB instead of IP failover is preferable for ensuring high availability of pods and services.

networking/metallb/about-metallb.adoc

@@ -39,12 +39,6 @@ include::modules/nw-metallb-layer2-limitations.adoc[leveloffset=+2]
 // BGP limitations
 include::modules/nw-metallb-bgp-limitations.adoc[leveloffset=+2]
 
-// Incompat with IP failover
-[id="incompatibility-with-ip-failover_{context}"]
-=== Incompatibility with IP failover
-
-MetalLB is incompatible with the IP failover feature. Before you install the MetalLB Operator, remove IP failover.
-
 [role="_additional-resources"]
 [id="additional-resources_about-metallb-and-metallb-operator"]
 == Additional resources