MetalLB Controller
- Canonical Kubernetes
- Containers
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 20 | 16 Dec 2021 | |
| latest/candidate | 18 | 03 May 2021 | |
| latest/beta | 20 | 13 Dec 2021 | |
| latest/edge | 21 | 02 Feb 2022 |
juju deploy containers-metallb-controller
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
-
iprange | string
Default: 192.168.1.240-192.168.1.247
For the Layer 2 Configuration only. This is the IP range from which MetalLB will have control over and choose IPs from to distribute to kubernetes services requesting an external IP of type Load Balancer. The ip range can be specified as a range (i.e 192.168.1.240-192.168.1.247") or as a CIDR (i.e "192.168.1.240/29") To be able to specify more than one ip pool, only the CIDR notation can be used (i.e "192.168.1.88/31,192.168.1.240/30").
-
protocol | string
Default: layer2
Type of configuration to use to announce service IPs. Upstream MetalLB supports both Layer 2 and BGP configuration. This charm currently only support the option 'layer2'. The layer 2 configuration works by responding to ARP requests on your local network directly, to give the machine's MAC address to clients.