Promoting Common Standards Without Sacrificing Tenant Autonomy

on YouTube ↗05m

" summary

Platform engineers present a practical middle ground: V cluster spins a certified Kubernetes control plane inside a pod per tenant, giving teams full cluster APIs while the host cluster retains shared services like Istio, Ingress and OPA. Isolation comes from NetworkPolicies and resource quotas configured in vcluster.yaml, and deployment works via V cluster CLI or Helm/Argo/Terraform. The claim is that tenants keep autonomy without breaking common standards; demos and configs are reusable across a fleet of virtual clusters.

AI-written summary · about

" related talks

• 37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive GuideLukas Gentele · ContainerDays Conference 2024
• 05mKeynote: How To Be A Good Landlord: Making Your Kubernetes Tenants HappyLukas Gentele · KCD New York 2024
• 51mMulti-tenant KubernetesMikhail Sidorov · Saint HighLoad++ 2022
• 32mFlexible Kubernetes Multitenancy with vClusterPiotr Zaniewski · SREday London 2025 Q3
• 23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancyHrittik Roy · SREday London 2024
• 34mBeyond Namespaces: Virtual Clusters are the Future of Multi-TenancyLukas Gentele · KubeCon + CloudNativeCon North America 2021
• 35mRunning Isolated VirtualClusters With Kata & Cluster APIChris Hein, Eric Ernst · KubeCon + CloudNativeCon North America 2022
• 23mVcluster - How we Put a Virtual Kubernetes Cluster Inside Another KubernetesPratik Jagrut · ContainerCon @ Open Source Summit Europe 2022