vcluster creates virtual Kubernetes clusters inside a host Kubernetes cluster. It isolates tenants at the Kubernetes API-server level, giving development teams cluster-like control without requiring a separate physical cluster. section 6.3.1
Use vcluster when teams need isolated Kubernetes environments:
- Provide each tenant with an isolated Kubernetes API server and freedom to install tools without affecting other tenants. section 6.3 section 6.3.1
- Choose vcluster when teams require cluster-wide Kubernetes API access; use namespaces when that access is unnecessary. section 6.3.1
- Create a virtual cluster with the vcluster Helm chart or use the vcluster CLI to create and connect to one. section 6.3.1
Provision and connect to a development environment
A platform can accept an Environment resource, use a Crossplane composition with the Crossplane Helm provider to provision a vcluster, and install the Conference application by default. Teams can inspect readiness with `kubectl get environments`, then connect with `vcluster connect team-a-dev-env-jp7j4 --server https://localhost:8443 -- zsh`. section 6.3.2
