Designing a Multitenancy Kubernetes Strategy That Fits Your Org
Talkat Multi-TenancyCon Europe 2024 · on Tuesday, 2024-03-19· at 10:25· Pavilion 7 | Level 7.3 | Room S02·
summary
Enterprise guidance for when to consolidate or isolate clusters: recommends using soft vs hard multitenancy to decide trust boundaries, namespace + NetworkPolicy + quotas for tenant isolation, and virtual clusters when apps need cluster‑wide privileges. Calls out concrete tooling: OPA Gatekeeper or Kyverno for policy, Paralus and Carpenter for RBAC-at-scale and node autoscaling, and Prometheus for chargeback metrics. Emphasizes measuring cluster unallocated capacity and namespace request vs utilization before resizing.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:54Agenda
- 6:20Host Cluster
- 6:57SelfService
- 7:43Control Access
- 9:45Tenant Isolation
- 11:45Policy Enforcement
- 14:48Cost Optimization
- 15:15Chargeback
- 16:45Optimization
- 19:32Questions
related talks
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
51mMulti-tenant Kubernetes
40mMulti-tenancy in Kubernetes
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
33mKubernetes Multi-tenancy: Principles and Practices for Large Scale Internal Deve...
36mKubernetes, Decisions
32mClusters wla Namespaces? Kifach blan Multitenancy f Kubernetes
26mThe Future of Multi-Tenancy in Kubernetes