Virtual Kubernetes Cluster
summary
Describes vcluster as a control plane that runs as a pod inside a host Kubernetes namespace, using k3s + sqlite default for the apiserver and datastore, with no scheduler; a syncer sinks pods to host where the host scheduler places them and mirrors status back. Higher-level objects (Deployments, CRDs) stay virtual, pods are renamed with virtual-namespace and vcluster suffixes, and a vcluster can be created or deleted in seconds versus the usual 10–20 minute full-cluster setup — useful for dev sandboxes and parallel CI/CD testing.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:43Challenges for Product Development Team
- 1:09Development Environment - Namespace
- 2:02Development Environment - Cluster
- 2:51Development Environment- Namespace Vs Cluster Isolation
- 3:21Less freedom of choice for developers
- 4:15Less flexibility in CI/CD pipelines
- 6:16What is vcluster? - Control Plane
- 8:18Demo - Quick Start
- 13:21vcluster Architecture
- 19:52Kubernetes Resources inside vcluster
- 20:58Network & DNS inside vcluster -Pod, Service
- 24:03Namespace Vs Cluster Vs vcluster
- 24:25Use Cases
- 25:40Documentation and Support
related talks
23mVcluster - How we Put a Virtual Kubernetes Cluster Inside Another Kubernetes
01h 47mKubernetes Virtual Clusters
34mBeyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy
32mFlexible Kubernetes Multitenancy with vCluster
23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancy
37mVirtual Clusters in the Real World: Lessons from k3k’s Journey to Production
35mMulti-Tenancy on Kubernetes with Virtual Clusters
20mKubernetes for the Virtualization Admin