Multi-tenant Kubernetes
summary
Three practical multitenancy patterns are compared—separate clusters, namespace-based (Capsule), and virtual control planes—along with concrete primitives used: RBAC, ResourceQuota, LimitRange, NetworkPolicy, and Pod security controls. A working virtual-cluster setup uses vcluster (syncer + optional k3s sidecar) to map tenant pods into one host namespace, enabling full API isolation while reusing host nodes; Capsule avoids naive namespace replication by introducing tenant objects. Tradeoffs: clusters cost more, vclusters need plugins for cloud LB and secrets and require an operator to scale.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:38Multi-tenancy terminology
- 8:26Resource isolation in Kubernetes
- 16:34Native object issues and solutions
- 22:20Control plane as a service
- 36:11Approach comparison and summary
- 39:29Q&A
related talks
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
40mMulti-tenancy in Kubernetes
26mThe Future of Multi-Tenancy in Kubernetes
35mMulti-Tenancy on Kubernetes with Virtual Clusters
24mMulti-Tenancy: Tips, Tricks, Tools And Tests
05mNamespace Multi-Tenancy, But All The Problems Related To It
30mMulti-Tenancy in Kubernetes: How We Avoided Clusters Sprawl W...
