# MetalLB

MetalLB is a self-hosted infrastructure app. A network load-balancer implementation for Kubernetes using standard routing protocols It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4650/metallb

## Description

A network load-balancer implementation for Kubernetes using standard routing protocols

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

74/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 1 day ago)
- Popular: 78 (8,411 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 68 (no serious findings, 12 minor, CI, tests, OpenSSF Scorecard 6.4/10)

## Links

- GitHub: https://github.com/metallb/metallb
- Kubernetes (Helm): https://artifacthub.io/packages/helm/metallb/metallb
- Official website: https://metallb.universe.tf
- Documentation: https://metallb.universe.tf/apis/

## Common questions

### Can I combine MetalLB with Traefik in a home Kubernetes cluster?

Yes, MetalLB and Traefik can work together to provide L7 routing to services in a home Kubernetes cluster.

### Will MetalLB work in a cluster that already has load-balancing functionality?

MetalLB requires a Kubernetes cluster that does not already have network load-balancing functionality.

### What traffic must be allowed between nodes for layer 2 mode?

In layer 2 mode, traffic on port 7946 TCP and UDP must be allowed between nodes, and the port can be configured to another value.

### Why might arping reach a MetalLB service from nodes or pods but not from an external VPS?

A MetalLB troubleshooting arping test can work from within a pod, node, or host while failing from an external VPS. That VPS may still be able to access the services.

---
Source: Our Local Host (https://ourlocalhost.com/app/4650/metallb), the self-hosted and open-source app directory.
