Back to Metallb

MetalLB Adopters

ADOPTERS.md

0.15.32.3 KB
Original Source

Note Do you want to add yourself to this list? Simply fork the repository and open a PR with the required change. We have a short description of the adopter types at the bottom of this page. Each adopter type is in alphabetical order.

MetalLB Adopters

TypeNameSinceWebsiteUse-Case
VendorCLASTIX2022linkMetalLB is used in Clastix Kubernetes Platform, as supported implementation of LoadBalancer on Bare Metal
End-user1&1 Mail & Media2018linkMetalLB is the main way to get network traffic into the clusters driving most of the internal services for WEB.DE, GMX and mail.com
End-userDeutsche Telekom AG2021linkMetalLB is used as the LoadBalancer in our own horizontal Telco Cloud platform Das SCHIFF / T-CaaS among several other use cases
VendorRed Hat, Inc.2022linkMetalLB is distributed together with Red Hat's Openshift containers platform, as the supported implementation of LoadBalancer services on Bare Metal
VendorSUSE2023linkMetalLB is a core part of the SUSE Edge solution serving as a LoadBalancer on Bare Metal, as well as load balancing the Kubernetes API in highly available topologies
VendorNokia EDA2024linkMetalLB implements the LoadBalancer controller role in the Nokia Event Driven Automation (EDA) product
End-userKiratech S.p.A.2022linkMetalLB is the LoadBalancer reference technology in our training courses laboratories, which are public and published under MIT license
End-userWestnet2023linkWe use MetalLB as the LoadBalancer for our in-house and public-facing applications, built on a self-hosted Talos Linux cluster

Adopter Types

End-user: The organization runs MetalLB in production in some way.

Integration: The organization has a product that integrates with MetalLB, but does not contain MetalLB.

Vendor: The organization packages MetalLB in their product and sells it as part of their product.