From befc6cd6500697f7ad9c95ab1db4101c342c86e5 Mon Sep 17 00:00:00 2001 From: Markus Opolka Date: Tue, 27 Jul 2021 17:46:45 +0200 Subject: [PATCH] Update MetalLB documentation (#7833) - Added a hint about the kube_proxy_strict_arp configuration, which is required for MetalLB to work - See also https://github.com/kubernetes-sigs/kubespray/pull/5180/files --- docs/metallb.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/metallb.md b/docs/metallb.md index e8165d2e8..984cd9bfa 100644 --- a/docs/metallb.md +++ b/docs/metallb.md @@ -4,6 +4,14 @@ MetalLB hooks into your Kubernetes cluster, and provides a network load-balancer It allows you to create Kubernetes services of type "LoadBalancer" in clusters that don't run on a cloud provider, and thus cannot simply hook into 3rd party products to provide load-balancers. The default operationg mode of MetalLB is in ["Layer2"](https://metallb.universe.tf/concepts/layer2/) but it can also operate in ["BGP"](https://metallb.universe.tf/concepts/bgp/) mode. +## Prerequisites + +You have to configure arp_ignore and arp_announce to avoid answering ARP queries from kube-ipvs0 interface for MetalLB to work. + +```yaml +kube_proxy_strict_arp: true +``` + ## Install You have to explicitly enable the MetalLB extension and set an IP address range from which to allocate LoadBalancer IPs.