MetalLB · Use

MetalLB assigns and advertises LoadBalancer addresses on the local network. It supplies the entry addresses used by Traefik and direct protocol services. It does not create public DNS records, configure the upstream router, or make a private address reachable from the Internet.

Access and audience

This is a platform service with no standalone user-facing website. Its consumers use Kubernetes resources or internal endpoints.

Your first workflow

Choose an unused address from METALLB_ADDRESS_POOL when a service needs a stable LoadBalancer IP. Keep that choice in apps/variables.yaml.
Declare the Service and its intended TCP/UDP ports. Use sharing annotations only when the services meet MetalLB’s sharing requirements.
Inspect Service events and the assigned address before troubleshooting the application above it.

Get help

Report the unreachable service and whether it fails from one network or all networks. Users do not need to select or modify load-balancer addresses.

During an interruption

An interruption can affect the applications that depend on this platform service. Ask the administrator to identify the affected service and expected recovery path.

Administrators can read the architecture and recovery limits.

Official documentation

Use the official MetalLB documentation for the complete feature reference. Some features depend on the installed version and options. If the manual differs from what you see, ask your administrator which version and features are enabled.

For antalos-specific state and availability, continue to Infrastructure Explanation. For installation and integration setup, use Deployment and Admin Guide.