MetalLB Controller

  • Canonical Kubernetes
Channel Revision Published Runs on
latest/stable 46 12 Jun 2023
Ubuntu 22.04 Ubuntu 20.04
latest/candidate 46 07 Jun 2023
Ubuntu 22.04 Ubuntu 20.04
latest/beta 41 21 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
latest/edge 44 22 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
1.28/candidate 46 07 Jun 2023
Ubuntu 22.04 Ubuntu 20.04
1.28/edge 44 22 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
1.27/stable 46 12 Jun 2023
Ubuntu 22.04 Ubuntu 20.04
1.27/candidate 46 12 Jun 2023
Ubuntu 22.04 Ubuntu 20.04
1.27/beta 41 10 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
1.27/edge 42 10 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
1.26/stable 37 27 Feb 2023
Ubuntu 22.04 Ubuntu 20.04
1.26/candidate 37 25 Feb 2023
Ubuntu 22.04 Ubuntu 20.04
1.26/beta 31 09 Apr 2023
Ubuntu 22.04 Ubuntu 20.04
1.26/edge 31 10 Nov 2022
Ubuntu 22.04 Ubuntu 20.04
1.25/stable 28 30 Sep 2022
Ubuntu 22.04 Ubuntu 20.04
1.25/candidate 28 28 Sep 2022
Ubuntu 22.04 Ubuntu 20.04
1.25/beta 32 01 Dec 2022
Ubuntu 22.04 Ubuntu 20.04
1.25/edge 23 08 Sep 2022
Ubuntu 22.04 Ubuntu 20.04
1.24/stable 17 04 Aug 2022
Ubuntu 22.04 Ubuntu 20.04
1.24/candidate 17 02 Aug 2022
Ubuntu 22.04 Ubuntu 20.04
1.24/beta 13 16 Jun 2022
Ubuntu 20.04
1.24/edge 18 12 Aug 2022
Ubuntu 22.04 Ubuntu 20.04
1.23/edge 9 25 Mar 2022
Ubuntu 20.04
juju deploy metallb-controller
Show information

Platform:

Learn about configurations >

  • 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.