MetalLB review
A focused, self-hosted load balancer for Kubernetes services outside cloud-provider integrations.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
MetalLB is an open-source network load-balancer implementation for bare-metal Kubernetes clusters. It assigns external IP addresses to Kubernetes LoadBalancer services from configured pools, then advertises those addresses through Layer 2 or BGP. Layer 2 mode uses ARP for IPv4 and NDP for IPv6, while BGP mode peers with network routers. It is intended for cluster operators without a cloud-provider load-balancer integration and fits teams that need Kubernetes-native service exposure on Linux-based, self-hosted infrastructure.
The project’s main strength is its focused networking model. Operators can allocate IPv4 and IPv6 addresses, configure behavior through Kubernetes custom resources, and choose between local-network announcements and router-based BGP advertisement. BGP multipath can distribute connections across multiple cluster nodes, while Layer 2 mode supports automatic leader failover when a node fails. BGP policy controls, including peer and service selectors, add configuration scope for environments that need more specific advertisement rules.
MetalLB is open-source and self-hosted rather than a vendor-managed load-balancing service, so its operational fit depends on the Kubernetes environment and surrounding network design. Deployment is supported through Kubernetes manifests, Kustomize, Helm, or an operator, but the cluster still needs configured IP address pools and compatible Layer 2 or BGP connectivity. Choose MetalLB when bare-metal Kubernetes service advertisement, address allocation, and node failover are the priority. Teams seeking a general-purpose load balancer beyond Kubernetes, or a managed service, should choose a different approach.
MetalLB pros and cons
- Where it wins
- Supports Layer 2 ARP/NDP announcements and BGP service advertisement
- Allocates IPv4 and IPv6 addresses from configured pools
- Provides BGP multipath balancing and Layer 2 node failover
- Where it doesn't
- Focused on Kubernetes rather than general-purpose load balancing
- Requires self-hosted deployment and cluster administration
- Needs configured address pools and suitable network integration
MetalLB fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.
Last updated · How we research and update