dhi.io/klipper-lb
Klipper Service Load Balancer
Service load balancer implementation for K3s that exposes services of type LoadBalancer using host ports, enabling simple load balancing for Kubernetes workloads without requiring an external cloud provider.
pushed 22 hours ago
linux/amd64, linux/arm64
25.29 MB
for linux/amd64
119
for linux/amd64
Active support
-
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 Klipper Service Load Balancer
Klipper Load Balancer is a service load balancer implementation for K3s, the lightweight Kubernetes distribution by
Rancher. It enables services of type LoadBalancer to work in K3s clusters without requiring an external cloud provider
by binding to host ports on the cluster nodes. This makes it straightforward to expose services externally in
on-premises or edge environments where cloud load balancers are not available.
For more details, see https://github.com/k3s-io/klipper-lb.
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 near-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
K3s is a CNCF Sandbox project. RKE2 is associated with SUSE Rancher. This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.