dhi.io/metallb-controller
MetalLB Controller
MetalLB controller component manages IP address allocations for LoadBalancer services on bare metal Kubernetes clusters.
pushed 1 day ago
linux/amd64, linux/arm64
56.42 MB
for linux/amd64
195
for linux/amd64
Active support
controller
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About MetalLB Controller
MetalLB is a load-balancer implementation for bare metal Kubernetes clusters, using standard routing protocols. The controller component is a Deployment that runs as a centralized control plane and is responsible for managing IP address allocations for LoadBalancer services. It watches for service changes and assigns IP addresses from configured pools, coordinating with the speaker components to announce these addresses to the network. The controller handles IP address management, service endpoint monitoring, and configuration validation.
For more information and official documentation, visit https://metallb.io
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with zero-known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
MetalLB® and the MetalLB® logo are trademarks of the MetalLB project. All rights in the mark are reserved to the MetalLB project. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.