admin/turingpi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ops(metallb): upgrade 0.13.12 -> 0.16.1, pin native L2 (no FRR)

Browse Source 
0.16.1 chart defaults frr.enabled=false but frrk8s.enabled=true, which
deploys a heavy frr-k8s daemonset. With no BGP peers (pure L2/ARP), FRR is
unnecessary and its images caused DiskPressure on the Pi nodes, evicting a
speaker and stalling the rollout. Disable both frr and frrk8s for a single
-container L2 speaker.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
gilgamezh
2026-05-31 11:13:59 +02:00
parent 1b3f34a432
commit 2c68a21d0b
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
non_argo_values/metallb_values.yaml
+13
View File
@@ -0,0 +1,13 @@
# MetalLB configuration for TuringPi K3s cluster
#
# L2 (ARP) mode only: the cluster advertises LoadBalancer IPs via the default
# IPAddressPool + L2Advertisement (resources/metallb.yml). There are no BGP
# peers, so FRR is not needed. Disable both the legacy embedded FRR and the
# newer frr-k8s daemonset -- their images cause DiskPressure on the small Pi
# nodes and add no value without BGP.
speaker:
frr:
enabled: false
frrk8s:
enabled: false