Operating a multi-tenancy Kubernetes service on KubeVirt
summary
Swisscom builds an on‑prem, multi‑tenant Kubernetes service using KubeVirt, Kube‑OVN, Trident‑CSI and Kubermatic KKP, deployed across four datacenters with one namespace mapped to one VPC and VLAN per tenant. The platform runs in production hosting over 300 clusters and ~2,000 VMs, uses an FRR edge‑router pod with BGP for north/south, metalLB/QLB for load balancing, supports VM live‑migration, and operates with ~10 engineers; the stack proves stable and enables hundreds of migrations within a year.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 3:17Why build a custom Kubernetes platform
- 7:09Cubert and multi-tenancy setup
- 10:19Cube OVN networking architecture
- 13:29Kubernatic KKP fleet management
- 17:28Cubeb and MetalLB for load balancing
- 20:16Lessons learned after one year
- 23:26Future roadmap and expansion plans
- 25:32Q&A session begins
related talks
25mKubeVirt: Converge IT infrastructure into one single Kubernetes platform
37mHigh Performance Networking with Kubevirt
36mIt’s All for the Users. More Durable, Secure, and Pluggable. KubeVirt v0.53
43mMaking Running Virtual Machines in a Kubernetes Cluster a Mainstream Activity
27mHigh Performance KubeVirt in Action
31mKubeVirt: What If Kubernetes Orchestrated Your VMs?
28mHow We Tackle KubeVirt’s Growth and Scalability
43mKubeVirt - Kubernetes, Virtualization and Your Future Data Center