Multi-Tenancy in Kubernetes: Best Practices Today, and Future Directions
summary
Explains a concrete taxonomy (enterprise, Kubernetes-as-a-service, hosted-app instances) and maps each to exact controls: RBAC, PodSecurityPolicy, NetworkPolicy, ResourceQuota, requests/limits, taints/tolerations, anti‑affinity/sole‑tenant nodes and sandbox runtimes like gVisor or Kata. States cluster‑per‑tenant becomes unmanageable at thousands of tenants and advocates intra‑cluster sharing. Describes alpha priority and preemption that kills lower‑priority pods to free capacity and a proposed security profiles system to bundle versioned, portable policy sets for turnkey secure clusters.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:17What is multi-tenancy?
- 0:54Why within a cluster?
- 4:43Enterprise
- 17:38Multi-tenancy features: authentication and authorization
- 19:52Multi-tenancy features: PodSecurity Policy
- 21:05Multi-tenancy features: Network Policy
- 29:52Priority and preemption (alpha)
- 32:45Scheduling Policy
- 35:54Summary
- 36:15How to get involved
related talks
40mMulti-tenancy in Kubernetes
40mPanel Discussion: Multi-Tenancy in Kubernetes: Current State and Future Roadmap
51mMulti-tenant Kubernetes
24mMulti-Tenancy: Tips, Tricks, Tools And Tests
26mThe Future of Multi-Tenancy in Kubernetes
05mNamespace Multi-Tenancy, But All The Problems Related To It
20mDesigning a Multitenancy Kubernetes Strategy That Fits Your Org
51mMultitenant Kubernetes: squeezing out maximum efficiency