SkillsApr 16, 2026·3 min read

vCluster — Virtual Kubernetes Clusters Inside Real Clusters

vCluster creates lightweight virtual Kubernetes clusters that run inside namespaces of a host cluster, giving teams isolated environments without the cost and complexity of separate physical clusters.

AI Open Source
AI Open Source · Community
Agent ready

Review-first install path

This asset needs a review step. The copied prompt tells the agent to dry-run, show the writes, then proceed only after confirmation.

Needs Confirmation · 64/100Policy: confirm
Agent surface
Any MCP/CLI agent
Kind
Skill
Install
Single
Trust
Trust: Established
Entrypoint
vCluster Overview
Review-first command
npx -y tokrepo@latest install f23363bd-3942-11f1-9bc6-00163e2b0d79 --target codex

Dry-run first, confirm the writes, then run this command.

TL;DR
vCluster runs lightweight virtual Kubernetes clusters inside host cluster namespaces for team isolation without extra infrastructure costs.
§01

What it is

vCluster creates lightweight virtual Kubernetes clusters that run inside namespaces of a host cluster. Each virtual cluster has its own API server, control plane, and resource isolation, but shares the underlying host cluster's compute nodes. This gives teams their own Kubernetes environment without the cost of provisioning separate physical clusters.

It targets platform teams, DevOps engineers, and organizations that need to provide isolated Kubernetes environments for development, testing, or multi-tenancy without multiplying infrastructure costs.

§02

How it saves time or tokens

Provisioning a full Kubernetes cluster takes minutes to hours and costs real money. vCluster creates a virtual cluster in seconds using existing host resources. Teams get full admin access to their virtual cluster without risk to the host. Spinning up and tearing down environments for CI pipelines, feature branches, or experimentation becomes nearly free.

§03

How to use

  1. Install the vCluster CLI: brew install loft-sh/tap/vcluster or download from the releases page.
  2. Create a virtual cluster: vcluster create my-vcluster --namespace team-a.
  3. Connect to it: vcluster connect my-vcluster --namespace team-a — your kubeconfig switches to the virtual cluster.
§04

Example

# Create a virtual cluster for a feature branch
vcluster create feature-xyz --namespace dev

# Your kubectl now targets the virtual cluster
kubectl get nodes
# Shows synced nodes from host cluster

# Deploy and test in isolation
kubectl apply -f deployment.yaml
kubectl get pods

# Tear down when done
vcluster delete feature-xyz --namespace dev
§05

Related on TokRepo

§06

Common pitfalls

  • Virtual clusters share host cluster compute. Resource-heavy workloads in one vCluster can starve others. Use resource quotas on the host namespace.
  • Not all Kubernetes features work identically in virtual clusters. Node-level resources (DaemonSets, host networking) behave differently because the virtual cluster does not own physical nodes.
  • Networking between virtual clusters requires explicit configuration. By default, services in one vCluster are not reachable from another.

Frequently Asked Questions

How does vCluster differ from namespaces?+

Namespaces provide resource grouping within a single cluster but share the same API server, RBAC policies, and CRDs. vCluster gives each team a full Kubernetes API server with independent RBAC, CRDs, and control plane, while still running on shared host infrastructure. It provides stronger isolation than namespaces.

Can I run CRDs in a virtual cluster?+

Yes. Each virtual cluster has its own API server, so you can install CRDs without affecting the host cluster or other virtual clusters. This is a major advantage over namespace-based isolation where CRDs are cluster-scoped.

What is the resource overhead of a virtual cluster?+

A vCluster control plane (API server + etcd/SQLite + syncer) uses roughly 256MB-512MB RAM. This is significantly less than a full Kubernetes cluster. The workloads themselves use the same resources they would in a real cluster.

Does vCluster support persistent storage?+

Yes. vCluster syncs PersistentVolumeClaim requests to the host cluster's storage provisioner. Storage classes available on the host are accessible from the virtual cluster. Data persists as long as the host PV exists.

Can I use vCluster for multi-tenancy in production?+

Yes. vCluster is used in production for multi-tenant platforms where each tenant gets an isolated Kubernetes environment. Combined with network policies and resource quotas on the host, it provides a practical multi-tenancy model without dedicated clusters per tenant.

Citations (3)
Related on TokRepo
DevOps toolsSelf-hosted toolsFeatured workflows

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

Kubernetes Dashboard — Official Web UI for Kubernetes Clusters

Kubernetes Dashboard is the official general-purpose web-based UI for managing Kubernetes clusters, allowing you to deploy, troubleshoot, and manage containerized applications and cluster resources.

Skills
AI Open Source

KubeVirt — Run Virtual Machines on Kubernetes

KubeVirt extends Kubernetes with VM-native workloads. It lets you declare, schedule and manage traditional virtual machines as first-class Kubernetes objects alongside containers, sharing the same networking and storage.

Skills
AI Open Source

Virtual Kubelet — Run Kubernetes Pods on Serverless and External Backends

Virtual Kubelet implements the Kubernetes kubelet interface as a pluggable provider, allowing pods to be scheduled onto serverless platforms, IoT edge nodes, or any non-traditional compute backend.

Skills
AI Open Source

Sonobuoy — Kubernetes Cluster Diagnostics & Conformance Testing

A diagnostic tool that runs Kubernetes conformance tests and custom plugins to validate cluster health. Sonobuoy provides a non-destructive way to certify that clusters meet the Kubernetes specification and organizational standards.

Skills
AI Open Source
◈Home🔍Search👤Me