Quick Start

vCluster provisions isolated Kubernetes tenant clusters. The tenant clusters can go on your existing infrastructure, or they can be built from scratch on bare metal and VMs. Each tenant gets a full Kubernetes API experience while the virtualized control plane stays completely invisible to them.

group

Shared Nodes

You have a Kubernetes cluster and want isolated tenant environments. Tenant workloads run on the existing node pool. No extra infrastructure needed. Works with OSS CLI or Platform.

lock

Private Nodes

You need dedicated infrastructure per tenant. Each tenant cluster runs on its own nodes. Best for hard tenancy: GPU clouds, regulated platforms, and sovereign deployments. Requires vCluster Platform (free mode OK).

laptop

Docker (vind)

You want an ephemeral cluster for local development or CI. No Kubernetes required — just Docker.

storage

Standalone

You're building a managed Kubernetes platform from bare metal or VMs. Bootstrap a Control Plane Cluster and install Platform in one pass.

Match your situation to a guide

• Build a production Kubernetes platform from bare metal or VMs → Standalone
• Use an existing cluster for a GPU cloud, AI inference service, or regulated platform that needs dedicated infrastructure per tenant → Private Nodes
• Use an existing Kubernetes cluster for internal platforms, CI, or high-density production services → Shared Nodes
• Create a Kubernetes cluster on Docker for local development or CI → Docker (vind)

Still unsure? Read What is vCluster? to understand the deployment models and tradeoffs.