vCluster — Virtual Kubernetes Clusters Inside Real Clusters

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.

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.

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.

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

Related on TokRepo

• DevOps tools — Infrastructure automation and Kubernetes tooling
• Self-hosted tools — Run services on your own infrastructure

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.