Beyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy
Talkat KubeCon + CloudNativeCon North America 2021 · on Thursday, 2021-10-14· at 11:00· Room 502 AB + Online·
summary
v-cluster runs a full control plane as a pod inside a namespace: a statefulset with a separate API server and datastore (k3s + sqlite by default) plus a syncer that replaces the scheduler. the demo uses the vcluster CLI to create vc1, creates namespaces and deployments that actually schedule host pods because syncer copies pods (and selected ConfigMaps/Secrets/Services) into the host namespace. CRDs live per virtual cluster, different API versions can coexist, and the project is now a certified Kubernetes distribution.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:38What Are Kubernetes Namespaces?
- 4:31Hands up if you are a Kubernetes contributor!
- 5:43Multi-Tenancy? Why Should I Care?
- 9:14Virtual Clusters - Control Planes Running In Another Cluster
- 11:08Demo Virtual Clusters with
- 14:09Architecture Virtual Clusters with
- 17:11vcluster Creating Deployments
- 18:58vcluster What About Naming Conflicts?
- 19:37vcluster Syncer Only Syncs What Pods Need To Run
- 23:00vcluster Pod Networking & DNS
- 28:33Use Cases For Virtual Clusters
- 32:09Questions? Reach out!
related talks
26mVirtual Kubernetes Cluster
23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancy
23mVcluster - How we Put a Virtual Kubernetes Cluster Inside Another Kubernetes
32mFlexible Kubernetes Multitenancy with vCluster
01h 47mKubernetes Virtual Clusters
51mMulti-tenant Kubernetes
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
35mMulti-Tenancy on Kubernetes with Virtual Clusters