Skip to content

Commit eb4bbd2

Browse files
committed
TELCODOCS-1931 Describe source IP NAT for MetalLB return traffic
1 parent f233c60 commit eb4bbd2

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

modules/nw-metallb-when-metallb.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,9 @@ Using MetalLB is valuable when you have a bare-metal cluster, or an infrastructu
1010

1111
You must configure your networking infrastructure to ensure that network traffic for the external IP address is routed from clients to the host network for the cluster.
1212

13-
After deploying MetalLB with the MetalLB Operator, when you add a service of type `LoadBalancer`, MetalLB provides a platform-native load balancer.
13+
After deploying MetalLB with the MetalLB Operator, when you add a service of type `LoadBalancer`, MetalLB provides a platform-native load balancer.
14+
15+
When external traffic enters your {product-title} cluster through a MetalLB `LoadBalancer` service, the return traffic to the client has the external IP address of the load balancer as the source IP.
1416

1517
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.
1618

0 commit comments

Comments
 (0)