From 2c68a21d0ba385ca3fa193045de2f7232258699f Mon Sep 17 00:00:00 2001 From: gilgamezh Date: Sun, 31 May 2026 11:13:59 +0200 Subject: [PATCH] ops(metallb): upgrade 0.13.12 -> 0.16.1, pin native L2 (no FRR) 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 --- non_argo_values/metallb_values.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 non_argo_values/metallb_values.yaml diff --git a/non_argo_values/metallb_values.yaml b/non_argo_values/metallb_values.yaml new file mode 100644 index 0000000..88493b3 --- /dev/null +++ b/non_argo_values/metallb_values.yaml @@ -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