PureLB
purelb.io
- Free plan
- macOS
- Linux
- Self-hosted
What PureLB is
PureLB is a Kubernetes Service LoadBalancer for bare-metal Linux clusters. It assigns IP addresses from configured pools and announces them using Linux networking, with optional BGP for remote addresses. Each ServiceGroup uses one pool type: local, remote or Netbox. For local addresses, a Kubernetes Lease election selects the announcing node, and another can take over if it fails. Remote addresses are placed on a dummy interface on every node and advertised through BGP; an upstream router can distribute traffic across nodes using ECMP. ServiceGroups can include IPv4 and IPv6 pools for dual-stack deployments. Kubernetes Custom Resource Definitions configure address pools and node agents. PureLB can be installed with kubectl manifests or Helm, which the project recommends for production. Its Allocator and LBNodeAgent expose Prometheus metrics on port 7472 at /metrics. The Allocator runs as non-root with a read-only filesystem and no capabilities; LBNodeAgent runs as root with NET_ADMIN and NET_RAW capabilities on the host network. PureLB requires a Kubernetes cluster with an operational CNI and Linux nodes. Its Netbox integration is documented but currently unsupported and may not work with recent versions. The project is free and licensed under Apache License 2.0.
Who it suits
PureLB is intended for operators who run Kubernetes clusters on bare-metal Linux and need external reachability for LoadBalancer services.
Good to know, and what to watch
- Supports IPv4, IPv6 and dual-stack deployments.
- Local addresses can fail over to another node.
- Remote addresses can use BGP and ECMP.
- Installation is available through manifests or Helm.
- Prometheus metrics are exposed by both components.
- Requires Kubernetes with an operational CNI and Linux nodes.
- Netbox integration is unsupported and may fail with recent versions.
- LBNodeAgent runs as root with NET_ADMIN and NET_RAW capabilities.
The verdict
PureLB provides address allocation and announcement for bare-metal Kubernetes services, with local and BGP-based options. Its Linux and cluster requirements, plus the unsupported Netbox integration, are important deployment considerations.
What the maker publishes
- Address pools
- PureLB supports local, remote, and Netbox address pools, with each ServiceGroup configured for exactly one type. source
- Address types
- Local addresses are added to host interfaces, while remote addresses use a dummy interface and can be advertised through BGP. source
- BGP
- The default installation includes a k8gobgp sidecar for advertising remote addresses to upstream BGP routers; BGP can be disabled during installation. source
- Configuration
- PureLB uses Kubernetes Custom Resource Definitions for address pools and node agent configuration. source
- Configuration
- PureLB uses Kubernetes Custom Resource Definitions with schema validation to configure address pools, node agents, and BGP peering. source
- Installation
- PureLB can be installed with kubectl manifests or Helm; its documentation recommends Helm for production deployments. source
- Installation
- PureLB can be installed using kubectl manifests or Helm, and its documentation recommends Helm for production installations. source
- Integration
- PureLB can request IP addresses from Netbox, but its documentation says this integration is currently unsupported and may not work with recent Netbox versions. source
- Intended users
- PureLB is designed for operators running Kubernetes clusters on bare-metal Linux nodes who need external reachability for LoadBalancer services. source
- IP support
- PureLB supports IPv4, IPv6, and dual-stack deployments. source
- IPv4 and IPv6
- ServiceGroups can include both IPv4 and IPv6 pools, and PureLB supports dual-stack deployments. source
- License
- PureLB is licensed under the Apache License, Version 2.0. source
- License
- PureLB is licensed under the Apache License, Version 2.0. source
- Local addresses
- For local addresses, a Kubernetes Lease based election chooses one node to announce each address, and a new node can take over if the winner fails. source
- Monitoring
- The Allocator and LBNodeAgent expose Prometheus metrics on port 7472 at /metrics. source
- Monitoring
- PureLB exposes Prometheus metrics for the allocator and node agent and documents Prometheus Operator ServiceMonitors, alert rules, and a Grafana dashboard. source
- NetBox integration
- PureLB documents NetBox IP address management integration, but says the integration is currently unsupported, untested against recent NetBox versions, and may not work correctly. source
- Operations
- The optional kubectl-purelb plugin provides commands for pool utilization, service status, election state, BGP sessions, data-plane health, and configuration validation. source
- Purpose
- PureLB is a Kubernetes Service LoadBalancer for bare metal that allocates IP addresses from configured pools and announces them using Linux networking, with optional BGP. source
- Purpose
- PureLB provides Kubernetes LoadBalancer services for bare-metal deployments by allocating IP addresses from configured pools and announcing them through Linux networking or optional BGP. source
- Remote addresses
- Remote addresses are added to a dummy interface on every node and advertised through BGP; an upstream router can distribute traffic across nodes using ECMP. source
- Requirements
- PureLB requires a Kubernetes cluster with an operational CNI and Linux nodes because it uses the Linux netlink API. source
- Requirements
- PureLB requires a Kubernetes cluster with a working CNI and Linux nodes; BGP use also requires TCP port 179 connectivity to an upstream router. source
- Security
- The Allocator runs as non-root with a read-only filesystem and no capabilities; LBNodeAgent runs as root with NET_ADMIN and NET_RAW capabilities on the host network. source
Checked against the maker's pages on 11 Oct 2026.