diff --git a/asciidoc/guides/metallb-k3s.adoc b/asciidoc/guides/metallb-k3s.adoc index accc8119..a5b2b314 100644 --- a/asciidoc/guides/metallb-k3s.adoc +++ b/asciidoc/guides/metallb-k3s.adoc @@ -1,5 +1,5 @@ [#guides-metallb-k3s] -= MetalLB on K3s (using L2) += MetalLB on K3s (using Layer 2 Mode) :experimental: ifdef::env-github[] @@ -13,7 +13,7 @@ endif::[] MetalLB is a load-balancer implementation for bare-metal Kubernetes clusters, using standard routing protocols. -In this guide, we demonstrate how to deploy MetalLB in layer 2 mode. +In this guide, we demonstrate how to deploy MetalLB in layer 2 (L2) mode. == Why use this method @@ -31,9 +31,9 @@ The major advantage of the layer 2 mode is its universality: it works on any Eth == MetalLB on K3s (using L2) -In this quick start, L2 mode will be used, so it means we do not need any special network gear but just a couple of free IPs in our network range, ideally outside of the DHCP pool so they are not assigned. - -In this example, our DHCP pool is `192.168.122.100-192.168.122.200` (yes, three IPs, see <> for the reason of the extra IP) for a `192.168.122.0/24` network, so anything outside this range is OK (besides the gateway and other hosts that can be already running!) +In this quick start, L2 mode will be used. +This means we do not need any special network equipment but three free IPs within +the network range. == Prerequisites @@ -45,7 +45,13 @@ K3S comes with its own service load balancer named Klipper. You https://metallb. ==== * Helm -* A couple of free IPs in our network range. In this case, `192.168.122.10-192.168.122.12` +* Three free IP adressess within the network range. In this example `192.168.122.10-192.168.122.12` + +[IMPORTANT] +==== +You must make sure these IP addresses are unassigned. +In a DHCP environment these addresses must not be part of the DHCP pool to avoid dual assignments. +==== == Deployment