Configure MetalLB BGP service network

apps/metallb/templates/ipaddresspool.yaml

@@ -1,14 +1,10 @@
-# Tells MetalLB which IP addresses it's allowed to hand out to Services.
-# Pick a small range on your LAN that nothing else will ever assign —
-# especially your router's DHCP server. MetalLB doesn't coordinate with
-# your router or DHCP server at all; it just answers network requests for
-# whatever address a Service claims from this range. If it overlaps your
-# DHCP range, you'll eventually get two devices claiming the same IP.
+# Tells MetalLB which IP addresses it may assign to LoadBalancer Services.
+# This is a dedicated routed service range, not the nodes' 10.10.10.0/24 LAN
+# and not a DHCP pool. BGPAdvertisement announces only addresses actually in
+# use, while the MikroTik accepts those routes from the two workers.
 #
-# >> Ask Claude to help you pick this range before editing it — it needs
-#    to know your LAN's subnet and DHCP range, which it can't guess.
-#    A typical home LAN answer looks like "my router hands out
-#    192.168.1.100–192.168.1.199, so let's use 192.168.1.240–192.168.1.250."
+# The first and last few addresses remain reserved for future network use.
+# Argo CD takes .10 and the demo app takes .11; .12-.250 remain available.
 #
 # This file lives under apps/metallb/templates/ alongside MetalLB's own
 # Helm-installed resources, rather than as a separate app, because it
@@ -26,4 +22,4 @@ metadata:
     argocd.argoproj.io/sync-wave: "1"
 spec:
   addresses:
-    - 192.168.1.240-192.168.1.250 # EDIT ME — replace with your chosen range
+    - 10.10.60.10-10.10.60.250