ahmza.com/k8s-starter-pack
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Configure MetalLB BGP service network

Browse Source
This commit is contained in:
ahmza
2026-09-03 02:19:46 +01:00
parent 4cb6bc9ec4
commit 502de4fdf0
11 changed files with 186 additions and 173 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/metallb.yaml
+5 -8
View File
@@ -1,12 +1,9 @@
# MetalLB, installed like any other app: an Application pointing at
# apps/metallb, a Helm chart (see apps/metallb/Chart.yaml) that both pulls
# in the upstream MetalLB chart AND carries our own IPAddressPool and
# L2Advertisement as extra templates (apps/metallb/templates/). Once this
# syncs, the cluster can hand out real IP addresses to Services of type
# LoadBalancer — something bare-metal Kubernetes doesn't do on its own
# (that's normally a cloud provider's job). See docs/05-metallb.md for the
# full explanation and the setup questions you'll need to answer before
# this is actually useful.
# apps/metallb, a Helm chart (see apps/metallb/Chart.yaml) that pulls in the
# upstream chart and carries this cluster's IPAddressPool, BGPPeer, and
# BGPAdvertisement templates. Together they let the MikroTik route dedicated
# 10.10.60.x addresses to LoadBalancer Services—something bare-metal
# Kubernetes does not provide on its own. See docs/05-metallb.md.
#
# Everything — MetalLB's own resources (including its CRDs) and our two
# custom resources that depend on them — comes from this one Application,