Multi-Tenancy on Kubernetes with Virtual Clusters
summary
K3k provides lightweight virtual K3s clusters on Kubernetes using two architectures: virtual mode (a full in‑pod control plane that is CNCF-conformant) and shared mode (an agentless K3s with a Virtual Kubelet dataplane that schedules workloads onto host nodes). The demo highlights a single API server plus a three‑pod Virtual Kubelet daemonset with 70–80 second provisioning, and the talk compares isolation, operational cost, GPU/resource reuse, and synchronization complexity while introducing a virtual cluster policy CRD to control network, node‑selector and PSA settings.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:20Multi-tenancy definition
- 7:59Hard vs soft tenancy
- 12:36Why virtual clusters
- 15:51Existing solutions
- 17:59K3K origins
- 20:26Virtual vs shared mode
- 23:16Demo: create virtual cluster
- 33:36Virtual clusters pros and cons
related talks
37mVirtual Clusters in the Real World: Lessons from k3k’s Journey to Production
51mMulti-tenant Kubernetes
23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancy
40mMulti-tenancy in Kubernetes
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
32mFlexible Kubernetes Multitenancy with vCluster
35mRunning Isolated VirtualClusters With Kata & Cluster API
34mBeyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy