Quick Start

Two questions determine which quickstart is right for you.

Do you already have a Kubernetes cluster?

• Yes — your existing cluster becomes the Control Plane Cluster that hosts tenant cluster control planes. No additional infrastructure required.
• No — choose vind (Docker, for local development and CI) or vCluster Standalone (bare metal or VMs, for production).

How should tenant workloads run?

• Shared nodes — tenant workloads run on the existing cluster's node pool. Lower overhead, fastest to set up. Suited for developer environments and CI pipelines.
• Private nodes — each tenant cluster gets dedicated nodes. Full infrastructure isolation for GPU workloads and regulated environments.

Choose your guide

Shared Nodes

Existing Kubernetes cluster. Tenant workloads on shared infrastructure. Fast setup for internal platforms and CI.

Private Nodes

Existing Kubernetes cluster or Standalone. Dedicated nodes per tenant. GPU workloads, regulated environments.

Docker (vind)

No Kubernetes required. Complete cluster in Docker containers. Local development and CI pipelines.

AI Cloud / Standalone

Bootstrap a managed Kubernetes platform from bare metal. For AI cloud providers and neoclouds.

Not sure which path fits your environment? Read What is vCluster? to understand the deployment models and tradeoffs.