MetalLB
Purpose: For platform engineers, network engineers, documents the MetalLB service in openCenter-gitops-base.
metallb provides LoadBalancer service support on clusters that do not have a native cloud load balancer. In this repository it is deployed as a Helm release in metallb-system.
What This Repo Deploys
-
Namespace/metallb-systemwith privileged Pod Security labels -
HelmRelease/metallb -
Base values Secret:
metallb-values-base -
Optional override Secret:
metallb-values-override
When to Use It
-
You run bare-metal or private cloud clusters without a managed load balancer.
-
You want stable IPs for ingress controllers, gateways, or other edge services.
-
You want Layer 2 or BGP-based service advertisement managed inside Kubernetes.
Key Integration Points
-
Gateway API, ingress controllers, and service meshes often depend on MetalLB-provided IPs.
-
IP pools and BGP peers are usually cluster-local manifests, not base values.
Example
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
name: public-pool
namespace: metallb-system
spec:
addresses:
- 192.0.2.100-192.0.2.120
Configuration Surfaces
-
Service path:
applications/base/services/metallb/ -
Namespace:
metallb-system -
Flux object:
HelmRelease/metallb -
Base values Secret:
metallb-values-base -
Override values Secret:
metallb-values-override