Panel Discussion: Multi-Tenancy in Kubernetes: Current State and Future Roadmap
summary
Kubernetes lacks a formal multi-tenancy model; the working group catalogs use cases and publishes prototypes in the kubernetes-sig/multi-tenancy repo, outlining four architecture approaches (multi-cluster, single-cluster with tenant CRDs, nested clusters, core API tenancy). Current field solutions use namespaces plus RBAC, NetworkPolicy and Pod Security Policies but hit cluster-wide limits (storage, CRDs, API scoping) and quota gaps. Active experiments include nested API servers (Alibaba), OPA/Gatekeeper policies, eBPF network plugins, Kata/container runtimes and node isolation patterns like node-assign or divider, aiming for soft multi-tenancy and hard multi-tenancy trade-offs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:08Panel Introductions
- 3:43MultiTenancy Working Group
- 7:00Soft vs Hard MultiTenancy
- 8:25Custom MultiTenancy
- 10:28Red Hat MultiTenancy
- 12:53Cray MultiTenancy
- 14:31VMware MultiTenancy
- 15:20Audience Questions
- 23:46Challenges
- 28:21Emerging technologies
related talks
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
26mThe Future of Multi-Tenancy in Kubernetes
40mMulti-tenancy in Kubernetes
24mMulti-Tenancy: Tips, Tricks, Tools And Tests
35mDeep Dive: Kubernetes Working Group for Multi-tenancy
23mKubernetes Working Group for Multi-Tenancy Project Overview
05mNamespace Multi-Tenancy, But All The Problems Related To It
51mMulti-tenant Kubernetes