Offer reserved GPU capacity through Private Nodes assigned to one tenant cluster at a time. vCluster Platform manages tenant access and capacity policy, while vMetal can supply bare metal Machines when physical capacity must be provisioned.
Reserved GPU services need clear ownership of worker capacity and a consistent way to deliver it to tenant clusters.
A separate Kubernetes management stack for every tenant increases infrastructure and operational work.
Namespace-only designs do not dedicate worker capacity or provide a separate tenant control plane.
Custom capacity workflows create manual handoffs between tenant requests, Machine provisioning, and cluster attachment.
vCluster Platform assigns Private Nodes to production tenant clusters and applies tenant access and capacity policy centrally. vMetal can provision physical Machines when additional bare metal capacity is required.
Reserved GPU capacity combines dedicated Private Nodes, tenant control planes, capacity policy, and optional Machine provisioning.
Private Nodes dedicate worker capacity, networking, and storage to one production tenant cluster at a time.
Each tenant receives its own virtualized Kubernetes control plane, API server, and RBAC boundary.
Auto Nodes can create and delete Machine requests to maintain configured Private Node capacity based on supported resource requirements.
vMetal provisions physical Machines behind a stable API and can join completed servers to the target tenant cluster automatically.
Manage tenants, access, templates, quotas, capacity policy, and fleet observability through one UI, CLI, and API.
This isn’t a side project. Behind every vCluster deployment is 5+ years of deep K8s engineering, security hardening, and battle-tested infrastructure work at massive scale.
Talk to our team about your stack
Deploy vCluster on your infra in minutes
Go live with a hyperscaler-grade tenant experience in days
Private Nodes assign dedicated worker capacity to one production tenant cluster at a time. Each tenant also gets its own virtualized control plane and RBAC boundary, while capacity policy controls which node types the tenant can request.
No separate Kubernetes control-plane servers are required for each tenant. Private Nodes provide dedicated worker capacity, and the tenant control plane runs as isolated pods on the control plane cluster.
Reserved capacity can back managed Kubernetes, Slurm, Run:AI, Ray, inference, and other cluster products. vCluster provides the tenant boundary, while Slurm and Run:AI remain responsible for their scheduling capabilities.
Launch time depends on whether the reserved nodes already exist or must be provisioned. vCluster provides the tenant cluster and capacity workflow, while the selected Machine driver determines infrastructure provisioning time.
Private Nodes provide tenant-scoped networking. When Metal3 and Netris are configured, separate network environments can also provide hardware-backed L2 isolation.
vCluster powers 100K GPUs across 50+ GPU Clouds & Fortune 500s and is validated in the NVIDIA DGX reference architecture.
See how vCluster Platform supports reserved gpu capacity for ai clouds.
