Running Isolated VirtualClusters With Kata & Cluster API
summary
Demonstrates a working setup that runs per-tenant Kubernetes control planes inside one supercluster using vCluster and Cluster API, and isolates workloads by running pods in Kata containers with per-tenant iptables pushed from a cube-proxy exporter to a VN agent inside each guest. Shows routable tenant Service CIDRs (example: tenant services 10.32.x.x, pod IPs 192.168.x.x), automatic runtime injection, a VC Sinker syncing pod-schedulable objects, and plans to replace iptables sync with kpng for scale.
AI-written summary · about
chapters (8)
- 0:00Multi-tenant Kubernetes challenges
- 1:46Control plane multi-tenancy with VirtualCluster
- 8:32Data plane isolation with Kata Containers
- 12:44Routable services in isolated clusters
- 17:14Live demo: VirtualCluster with Kata
- 25:46Scaling networking with KPING
- 27:11Limitations and next steps for hard multi-tenancy
- 34:14Q&A
related talks
37mVirtual Clusters in the Real World: Lessons from k3k’s Journey to Production
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
35mMulti-Tenancy on Kubernetes with Virtual Clusters
51mMulti-tenant Kubernetes
32mFlexible Kubernetes Multitenancy with vCluster
22mTaming the VM Sprawl: KCP Meets KubeVirt
23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancy
34mBeyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy
