Kubermatic Load Balancer (KubeLB) is a cloud-native, multi-tenant load balancing solution that centrally manages Layer 4 and Layer 7 load balancing configurations for Kubernetes clusters across multi-cloud, on-premises, and edge environments.
The Kubermatic Load Balancer Accelerator helps you implement a state-of-the-art, carrier-grade load balancing solution. Our experienced architects provide strategic and operational guidance at all stages of the process to avoid common networking pitfalls and ensure a successful, secure, and smooth implementation of KubeLB.
The Accelerator covers five engagement phases:
Explore -> Deploy -> Enablement -> Testing -> Touchdown
1. Explore
Our architects engage with your team to review your current network architecture, analyze your multi-cluster requirements, and align your load balancing strategy with the technical capabilities of Kubermatic Load Balancer.
Typical Activities
- Kickoff workshop: Define project scope, stakeholders, and success criteria.
- Architecture review: Assessment of current networking setup (BGP, Layer 2, etc.) and ingress requirements.
- Requirement analysis: Determine needs for Layer 4 (TCP/UDP) vs. Layer 7 (HTTP/HTTPS, Gateway API) load balancing.
- Topology planning: Define the Management Cluster and Tenant Cluster relationships.
Deliverables
- List of networking and infrastructure requirements.
- High-level architectural design for the KubeLB deployment.
- Documentation of PoC scope and implementation timeline.
2. Deploy
During this phase, our architects work hands-on to ensure that Kubermatic Load Balancer is successfully deployed and integrated into your environment.
Typical Activities
- Management Cluster Setup: Installation of the KubeLB Manager and Control Plane.
- Tenant Cluster Integration: Deployment of the KubeLB Cloud Controller Manager (CCM) agents on tenant clusters.
- Network Configuration: Configuration of BGP peering, LoadBalancer Classes, and routing between clusters.
- Gateway & Ingress Setup: Configuration of Gateway API and Ingress controllers for application traffic.
Deliverables
- Fully functional KubeLB Management Cluster.
- Connected Tenant Clusters with active CCM agents.
- Documentation of the deployment configuration and network topology.
3. Enablement
In the enablement phase, our architects hand over the Kubermatic Load Balancer (KubeLB) installation to your team, ensuring they are equipped to operate and manage it effectively.
Typical Activities
- Operational Workshops: Training on managing tenants, configuring LoadBalancer services, and using the kubelb CLI.
- Traffic Management Training: Deep dive into advanced traffic management (Rate Limiting, Circuit Breaking, Failover).
- Security Enablement: configuring Certificate Management (Cert-Manager), DNS automation, and mTLS.
- Observability Setup: Reviewing metrics, logs, and traces for load balancing traffic.
Deliverables
- Trained operations team capable of managing KubeLB.
- Customized operational runbooks (e.g., adding new tenants, troubleshooting connectivity).
- Concept papers for long-term load balancing strategy.
4. Testing
Our architects work closely with your team to ensure that Kubermatic Load Balancer is effectively operating under real-world conditions.
Typical Activities
- Functional Testing: Verification of Layer 4 (TCP/UDP) and Layer 7 (Ingress/Gateway API) traffic routing.
- Resilience Testing: Simulation of node failures, cluster disconnects, and BGP convergence tests.
- Performance Benchmarking: Basic load testing to verify throughput and latency requirements.
- Security Verification: Validation of tenant isolation and policy enforcement.
Deliverables
- List of tests performed based on PoC requirements.
- Documentation of test results, including performance metrics and failover validations.
5. Touchdown
Our architects will present the results of the setup and engage with your team to identify the next steps for a production rollout.
Typical Activities
- Touchdown Workshop: Presentation of results, lessons learned, and outlook.
- Roadmap Planning: Identification of next steps for production scaling and feature adoption.
- Final Handoff: Transfer of all remaining documentation and credentials.
Deliverables
- Executive presentation of results.
- List of prerequisites for production Go-live.
- Final architectural recommendations.
Duration
11.5 days
Prerequisites
To ensure a smooth Accelerator, the following prerequisites should be met:
- Management Cluster: A Kubernetes cluster (v1.25+) ready to host the KubeLB Manager.
- Tenant Clusters: One or more Kubernetes clusters to act as tenants.
- Network Infrastructure:
- For BGP mode: Access to upstream routers and BGP configuration details (ASN, Peers).
- For Layer 2 mode: A flat network allowing IP allocation.
- Access: SSH and kubectl access to all relevant clusters and nodes.
Enterprise Subscription
This Accelerator includes a Kubermatic Load Balancer Enterprise Subscription for the duration of the engagement (plus 2 months). The following details apply:
- 2 months subscription
- Full Feature Access: Includes Gateway API, Global Load Balancing, and Advanced Security features.
- Support: Access to Kubermatic enterprise support during the subscription period.