Multi-Tenancy in Kubernetes: How We Avoided Clusters Sprawl W...
summary
Capsule is an open-source Kubernetes operator that replaces per-customer clusters with a single-cluster-per-region model, avoiding the multiplicative “six clusters per customer” sprawl; it supplies a tenant CRD that enforces limitRanges, ResourceQuotas and NetworkPolicies across grouped namespaces, an enforced ingress/storage class mapping, and a bring-your-own-device node selector model. Wargaming integrates Capsule plus a capsule-proxy (kube-proxy fork) and a provisioner and runs it in production to isolate noisy neighbors, enable billing by node labels, and keep a vanilla kubernetes UX.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:55Introduction about the Multi-Tenancy Dilemma and the Current State of Multi-Tenancy in Kubernetes
- 3:19Limit Range
- 3:53Resource Quota
- 22:02Provisioner
- 22:54Shared Ingresses
- 23:32Isolation
- 24:48Capsule Proxy
- 28:33Lens Extension
related talks
05mProject Lightning Talk: Capsule: Launching Multi-Tenancy to New Kubernetes Horizons
05mNamespace Multi-Tenancy, But All The Problems Related To It
51mMulti-tenant Kubernetes
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
40mMulti-tenancy in Kubernetes
26mThe Future of Multi-Tenancy in Kubernetes
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
29mManaging a Multi-Tenanted Kubernetes Cluster in Production