metallb-controller

Infra

Updated on July 26

MetalLB-Controller Overview

Secure your stack with a hardened MetalLB-Controller image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

MetalLB is a load balancer implementation for bare-metal Kubernetes clusters. The MetalLB-Controller is the cluster-wide component responsible for IP address allocation. It watches Services of type LoadBalancer and assigns addresses from configured pools, coordinating with MetalLB Speaker nodes to announce them.

Try It Out

Prerequisites

A running Kubernetes cluster (v1.21 or higher is recommended)
Helm v3.8 or higher for OCI support (Installation instructions)
kubectl installed and configured

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Add Repository to your Local Client

Add the Helm chart to your local Helm client.

helm repo add metallb https://metallb.github.io/metallb
helm repo update

Step 3: Deploy via Helm Chart

helm install metallb metallb/metallb \
  --namespace metallb-system \
  --create-namespace \
  --set controller.image.repository=reg.mini.dev/metallb-controller \
  --set controller.image.tag=latest \
  --set controller.image.pullPolicy=Always

Check that all Pods are up and running:

kubectl get pods -n metallb-system

Confirm that Minimus images were deployed:

kubectl -n metallb-system describe pods -l app.kubernetes.io/component=controller | grep Image:

Clean Up

Uninstall the chart to delete the namespace and its resources, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:

helm uninstall metallb -n metallb-system

Technical Considerations

The MetalLB-Controller image provided by Minimus is a slim, security-hardened alternative to the public image from Quay.io. The images are largely interchangeable, with a few differences as noted below.

MetalLB-Controller built by Minimus:

Runs as root to support required functions in alignment with the public image.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.