Skip to content

Commit

Permalink
Merge pull request #62022 from openshift-cherrypick-robot/cherry-pick…
Browse files Browse the repository at this point in the history 
…-61903-to-enterprise-4.11

[enterprise-4.11] OCPBUGS-15307: Clarity around MetalLB address resolution for L2
  • Loading branch information
@mburke5678
mburke5678 committed Jul 5, 2023
2 parents 8e53963 + 255e89e commit fa35e38
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion modules/nw-metallb-layer2.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,10 @@

In layer 2 mode, the `speaker` pod on one node announces the external IP address for a service to the host network.
From a network perspective, the node appears to have multiple IP addresses assigned to a network interface.

[NOTE]
====
Since layer 2 mode relies on ARP and NDP, the client must be on the same subnet of the nodes announcing the service in order for MetalLB to work. Additionally, the IP address assigned to the service must be on the same subnet of the network used by the client to reach the service.
In layer 2 mode, MetalLB relies on ARP and NDP. These protocols implement local address resolution within a specific subnet. In this context, the client must be able to reach the VIP assigned by MetalLB that exists on the same subnet as the nodes announcing the service in order for MetalLB to work.
====

The `speaker` pod responds to ARP requests for IPv4 services and NDP requests for IPv6.
Expand Down

0 comments on commit fa35e38

Please sign in to comment.