Clusters wla Namespaces? Kifach blan Multitenancy f Kubernetes
summary
Compares isolation tradeoffs with concrete numbers and outcomes: namespaces with RBAC and quotas are cheap and let one cluster serve tens or hundreds of tenants but leak noisy‑neighbor and policy risks when tenants run mutable workloads; virtual clusters (per‑tenant API server and virtualized nodes) give strong isolation and eliminate cross‑tenant resource interference at the cost of higher operational and cloud bills — dozens to hundreds of extra control‑plane instances; recommends a hybrid approach (namespaces + virtual clusters for high‑risk tenants) and notes no live demo due to time.
AI-written summary · about
chapters (11)
- 0:00Introduction and thanks
- 3:12Historical context of multitenancy
- 8:30Mainframes and early multitenancy
- 11:50Cloud computing and evolution
- 15:41Introduction to Kubernetes and clusters
- 18:22Namespaces in Kubernetes
- 21:17Communication between namespaces
- 23:58Virtual clusters vs namespaces
- 27:22Kubernetes cluster structure
- 29:58Cost and organizational considerations
- 31:25Q&A and closing remarks
related talks
51mMulti-tenant Kubernetes
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
20mDesigning a Multitenancy Kubernetes Strategy That Fits Your Org
26mThe Future of Multi-Tenancy in Kubernetes
05mNamespace Multi-Tenancy, But All The Problems Related To It
34mBeyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy
40mMulti-tenancy in Kubernetes
24mMulti-Tenancy: Tips, Tricks, Tools And Tests