Single-Tenant Per Customer

Give each enterprise customer their own complete cluster stack. Dedicated nodes, an isolated tenant cluster, and full cluster-admin access if you choose to offer it. Your platform team handles provisioning and lifecycle. Customers see only their own environment.

Typical stack: Platform + private nodes per customer. vMetal optional for physical server fleets. vNode for customers requiring privileged workload support.

What makes this path different: Each customer is fully isolated at the node level. Customers may have cluster-admin rights to their own cluster while remaining invisible to each other and to the platform layer. This path is closely related to the AI Cloud path. The main distinction is whether your customers consume Kubernetes directly (this path) or through your own product API (AI Cloud).

Day 0: Design decisions

Decision	Read next	Outcome
Define per-customer node allocation	Private Nodes, Auto Nodes	Each customer cluster maps to a dedicated node pool. Auto Nodes provisions and reclaims nodes as customers are added or removed.
Plan provisioning automation	Templates, Terraform	Customer cluster creation is triggered by your CRM or provisioning system, not by manual Platform operations.
Define offboarding and node reclaim	Manage private nodes, vMetal docs	Document how nodes are reclaimed and reimaged when a customer offboards.

Day 1: Stand up the first customer cluster

1. Install vCluster Platform.
2. Configure Auto Nodes or vMetal for automated node provisioning and reclaim.
3. Create a per-customer cluster template with private nodes, backing store, and HA.
4. Wire provisioning automation to Platform via Terraform, CLI, or API.
5. Validate the full customer lifecycle: provision, validate isolation, access as cluster-admin, offboard, and verify node reclaim.

Day 2: Operate

Operation	Read next
Add and remove customers	Auto Nodes, provisioning automation
Back up and restore per-customer	Snapshots, restore
Upgrade customer clusters	Upgrade vCluster