Lab: Enable Supervisor & Deploy a VKS Cluster
Objectives
- Enable a Supervisor on VDS networking with the Foundation Load Balancer (Obj 4.1)
- Create a vSphere Namespace with storage policy, VM classes, content library and limits
- Deploy a VKS cluster and an app with a vSAN-backed persistent volume
Prerequisites
Holodeck VVF 9.0 instance deployed and healthy
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX. Supervisor and VKS sizing must fit the physical Holodeck host.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Enable the Supervisor and deploy a VKS cluster
Enable a Supervisor on the vSphere cluster, create a vSphere Namespace, deploy a VKS cluster, and deploy an application with vSAN storage.
In vCenter, configure Supervisor Service on vSphere cluster
Select the vDS; assign the Management network port group and one or more Workload network port groups (VLAN-backed); enter a non-overlapping Services CIDR (an internal range, not a VLAN — this lab configures no pod network and uses only the VM Service and VKS clusters. The VCF 9.0 docs conflict on vSphere Pods for a VDS-networked Supervisor: 'What Is a vSphere Pod?' (p.5212) says "vSphere Pods are only supported with Supervisors that are configured with NSX as the networking stack", while 'Add a Load Balancer to a Simplified Supervisor Deployment' (p.5311, p.5314) says "Adding a load balancer enables use of the vSphere Pods and Supervisor Services in addition to the VM Service". Treat NSX as the documented baseline and confirm vSphere Pod support on your build)
Configure the load balancer for the Supervisor API: Foundation Load Balancer (in-box in 9.0) or Avi — HAProxy is deprecated in 9.0 (p.240)
Verify the Supervisor is Running (one control-plane VM, or three when deployed for HA — p.5549)
Create the vSphere Namespace first: Supervisor Management → Namespaces → New Namespace (VCF 9.0.1 docs p.5659); select the Supervisor and workload network, then add the vSAN storage policy, VM classes, a content library with VKr images, and CPU/memory/storage limits
kubectl vsphere login to the Supervisor, switch to the namespace context and apply a VKS Cluster manifest (1 or 3 control-plane nodes, 3 workers — see vvf-admin-12 for the manifest)
Wait for the cluster to report Ready (kubectl get cluster -n <namespace>), then kubectl vsphere login with --tanzu-kubernetes-cluster-name to reach the VKS cluster
Inside the VKS cluster create a Kubernetes namespace for the app (quotas for the vSphere Namespace were set in step 5)
Deploy sample app (nginx) with vSAN persistent volume
Verify pod running, PVC bound to vSAN storage
Validation Gate
Check: After enabling Supervisor and deploying a VKS cluster: verify Supervisor health is green, kubectl can connect, and a test pod runs successfully
Expected: Supervisor shows 'Running' in vCenter. kubectl get nodes shows VKS worker nodes Ready. Test pod (nginx) deploys and responds on assigned IP.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Supervisor → Running in vCenter (1 or 3 control-plane VMs)
✓ VKS cluster → kubectl get nodes shows the nodes Ready
✓ App → nginx pod Running and its PVC Bound to a vSAN storage class
Cleanup / Restore
• Delete the app and the VKS cluster if not reused; keep the Supervisor for vvf-admin-10..12
Design Reflection (VCDX)
Container platform architecture on VCF is increasingly tested in VCDX defense. Panelists want to understand why you chose VKS over standalone Kubernetes, how the Supervisor's networking choice (VDS + Foundation Load Balancer/Avi on VVF versus NSX on VCF) shapes ingress and pod networking, and your resource sizing for Supervisor.
Requirements
- Enable Supervisor on VDS networking with a load balancer (Foundation Load Balancer or Avi) and the documented prerequisites
- Deploy VKS cluster from content library TKR images
- Validate Kubernetes connectivity and workload deployment
Constraints
- VVF has no NSX: the Supervisor uses VDS (VLAN-backed) networking with a load balancer; HAProxy is deprecated in 9.0
- Services CIDR and workload network ranges must not overlap with existing networks (no pod CIDR on vDS networking)
- Supervisor control plane resources depend on the chosen size and VM count (one or three control-plane VMs) — size from the Supervisor sizing table, not a fixed 12 vCPU / 48 GB
Assumptions
- The workload network VLAN(s) and the load balancer's IP range are routable from the physical network
- Content library has current TKR images
- Cluster has sufficient capacity for Supervisor + workloads
Risks
- Pod CIDR exhaustion limiting Kubernetes scaling
- Supervisor control plane failure from undersized cluster