Academy/vSphere Foundation 9.0 Administrator (2V0-16.25)/Lab: Enable Supervisor & Deploy a VKS Cluster
This lab targets VCF 9.0

Lab: Enable Supervisor & Deploy a VKS Cluster

VCF 9.0Intermediatevcp-foundation⏱ 150 min

VVF 9.0 administrator lab (2V0-16.25). Built for a Holodeck VVF instance.

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

SystemUsernamePassword
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Enable the Supervisor and deploy a VKS cluster

Supervisor and VKS (formerly TKG Service) deployment on VVF is a multi-step process involving VDS networking with a load balancer (Foundation Load Balancer or Avi), storage policies, and content libraries; on VCF the NSX networking option replaces the external load balancer. Understanding the prerequisites and configuration sequence prevents deployment failures.

Enable a Supervisor on the vSphere cluster, create a vSphere Namespace, deploy a VKS cluster, and deploy an application with vSAN storage.

Step 1

In vCenter, configure Supervisor Service on vSphere cluster

Step 2

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)

Step 3

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)

Step 4

Verify the Supervisor is Running (one control-plane VM, or three when deployed for HA — p.5549)

Step 5

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

Step 6

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)

Step 7

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

Step 8

Inside the VKS cluster create a Kubernetes namespace for the app (quotas for the vSphere Namespace were set in step 5)

Step 9

Deploy sample app (nginx) with vSAN persistent volume

Step 10

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

Enabling Supervisor without the VDS networking and load-balancer prerequisites in place
Fix: A Supervisor on VDS networking (the VVF case — VVF has no NSX) needs: a management network for the control plane VMs, one or more workload networks (VLAN-backed distributed port groups), a load balancer (the built-in Foundation Load Balancer in 9.0, or Avi; HAProxy is deprecated), a non-overlapping Services CIDR, DRS fully automated plus HA, and a storage policy (VCF 9.0.1 docs p.5586, 'Deploying vSphere Supervisor with Foundation Load Balancer'). NSX networking (overlay transport zone, Tier-0, ingress/egress CIDRs) is the VCF option, not a VVF prerequisite. Missing any prerequisite makes enablement fail with networking errors — validate them first.
Allocating insufficient IP ranges for pod and service CIDRs
Fix: This lab configures no pod CIDR on vDS networking (the VCF 9.0 docs conflict on vSphere Pod support there; see step 2); size the Services CIDR (a private range — /16 in the documented VDS Supervisor requirements — unique per Supervisor and non-overlapping) and the workload network ranges for the VKS cluster node count, and give the load balancer a large enough VIP range for every cluster API endpoint and LoadBalancer service.
Not configuring a content library with VKr (VKS release) images
Fix: VKS clusters deploy from VKr images in the namespace's content library. If the library is empty or holds only versions the VKS service does not support, cluster creation fails. Subscribe the library to the published VKr images or import them.
Deploying Supervisor on a cluster with insufficient resources
Fix: The Supervisor deploys one control-plane VM, or three for HA (p.5549), at the size you choose; the cluster needs capacity for them plus workload headroom. On a 3-host cluster the Supervisor control plane (one or three VMs at the chosen size) consumes a meaningful share of the cluster — size it from the Supervisor sizing table and plan accordingly.

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

⚠ Known Pitfalls

Under-sizing the workload network and load-balancer VIP ranges — every VKS cluster node takes a workload-network address and every cluster API / LoadBalancer service takes a VIP.
Forgetting that the Supervisor control plane (one VM, or three for HA — p.5549) consumes resources on the host cluster that must be sized in.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.