MetalLB
metallb.io
- Free plan
- Linux
- Self-hosted
What MetalLB is
MetalLB provides network load balancing for Kubernetes clusters that do not run on a cloud provider. It assigns service IP addresses from operator-configured pools and announces them through ARP, NDP, or BGP, depending on the chosen mode. In layer 2 mode, one cluster machine announces a service address using ARP for IPv4 or NDP for IPv6. In BGP mode, cluster machines peer with nearby routers, which can distribute traffic across multiple nodes. The recommended FRR-K8s mode supports BFD, IPv6, and merging additional FRR configuration. MetalLB is free and open source, with no paid plans listed. It can be installed with Kubernetes manifests, Kustomize, or Helm, and an Operator is available on OperatorHub. It stays idle until configured with resources such as an IPAddressPool in its deployment namespace. Requirements include Kubernetes 1.13.0 or later, a compatible cluster network, and IPv4 addresses. The project describes itself as beta, and its configuration format may change incompatibly.
Who it suits
MetalLB suits operators who need load balancing for Kubernetes clusters outside cloud-provider environments. It requires configuration and a compatible cluster network.
Good to know, and what to watch
- Free and open source
- Supports ARP, NDP, and BGP announcements
- BGP can distribute traffic across multiple nodes
- Installable with manifests, Kustomize, or Helm
- Generally incompatible with cloud providers
- Requires configuration before it becomes active
- Project is beta; configuration may change incompatibly
- Speaker pod requires elevated network permissions
Plans
Every plan and priceMetalLB
Open source
The verdict
MetalLB offers address allocation and announcement modes for self-managed Kubernetes environments, with several installation paths. Check its compatibility and configuration requirements, and account for the project’s stated beta status.
What the maker publishes
- Address allocation
- It assigns and unassigns service IPs from address pools configured by the operator. source
- Announcement modes
- It announces service addresses using ARP, NDP, or BGP, depending on the selected mode. source
- BGP
- BGP mode peers cluster machines with nearby routers and can distribute traffic across multiple nodes. source
- BGP backend
- The recommended FRR-K8s mode supports BFD, IPv6, and merging additional FRR configuration. source
- Cloud compatibility
- MetalLB is generally incompatible with cloud providers; its compatibility page lists AWS, Azure, DigitalOcean, and Google Cloud as unsupported. source
- Community and support
- The project provides a users mailing list and Slack channel, and ongoing development and maintenance are led by project maintainers. source
- Configuration
- MetalLB remains idle until configured with resources such as IPAddressPool in its deployment namespace. source
- Install options
- MetalLB can be installed using Kubernetes manifests, Kustomize, or Helm; an Operator is also available on OperatorHub. source
- Layer 2
- In layer 2 mode, one cluster machine announces a service IP using ARP for IPv4 or NDP for IPv6. source
- Maturity
- MetalLB describes itself as a beta project and says its configuration format may change incompatibly as the project develops. source
- Purpose
- MetalLB provides a network load balancer for Kubernetes clusters that do not run on a cloud provider. source
- Requirements
- The project lists Kubernetes 1.13.0 or later, a compatible cluster network, and IPv4 addresses as requirements. source
- Runtime privileges
- The speaker pod requires elevated permissions for its network functions. source
- Security changes
- Release notes report read-only root filesystems and disabled privilege escalation for containers that lacked those settings, and a fix for CVE-2025-22874. source
Checked against the maker's pages on 4 Oct 2026.