Academy/VCAP — VCF VKS (3V0-24.25)
VCF

VCAP — VCF VKS (3V0-24.25)

VCF 9.0vcap-advanced

Master Supervisor cluster deployment, TKG cluster lifecycle, networking, storage, and security for Kubernetes workloads on vSphere. Covers Tanzu Kubernetes Grid, persistent volumes, NSX integration, and production Day-2 operations.

3V0-24.25
VCAP
60
Questions
135m
Duration
300 (scaled score; Broadcom publishes no percentage or ceiling)
Pass Score
32
Objectives

Exam Blueprint Weights

Section titles, groupings and weights below are VCDX Academy study groupings, NOT the official Broadcom blueprint structure. Broadcom publishes no section weights. Always cross-check the official exam guide. Official exam guide ↗
Section 1 — Architecture
~15%
Section 2 — Cluster Lifecycle
~25%High Weight
Section 3 — Networking
~20%
Section 4 — Storage
~15%
Section 5 — Security and Operations
~25%High Weight

Version Evolution

vSphere Kubernetes Service (VKS) is the VCF 9.0 name for the Supervisor-based Kubernetes platform formerly delivered as vSphere with Tanzu / Tanzu Kubernetes Grid Service. Evolution: VCF 4.0 (vSphere 7) introduced Workload Management with the Supervisor and TKG Service clusters; VCF 5.x moved cluster provisioning to Cluster API with ClusterClass (TKC API retained alongside); VCF 9.0 ships VKS 3.3.1 with the v1beta1 Cluster API and built-in ClusterClass as the standard, NSX VPC networking for the Supervisor, VKr 1.28–1.32 images, Foundation Load Balancer for VDS Supervisors, the VCF CLI, and deprecates HAProxy, the TKC API, the Velero operator install and the SupervisorServiceDefinition package.

Learning Outcomes

  • Describe the VCF 9.0 Supervisor topology (control plane VM count and sizes, Management Zones, Spherelet, Supervisor Services, vSphere Namespaces, Regions and Zones) and the networking stacks (NSX VPC, NSX segments, VDS with Foundation Load Balancer or Avi)
  • Plan and validate Supervisor activation against the 9.0 minimum requirements (hosts, vCenter, NSX Manager, Edge cluster, networks, MTU, content library)
  • Provision, scale, autoscale and upgrade VKS clusters with the v1beta1 Cluster API and built-in ClusterClass, VKr versions and standard packages via the VCF CLI
  • Protect clusters with the Velero standard package (Schedule objects, Kopia) and explain what Velero does and does not back up
  • Design multi-tenant isolation across namespaces, NSX VPC, Antrea/NSX policies, Pod Security Admission, RBAC and identity providers, and troubleshoot activation and provisioning failures from the object chain

VKS Architecture & Components#

vSphere Kubernetes Service (VKS) is the Kubernetes layer of VCF 9.0: the vSphere Supervisor turns a vSphere cluster (or three clusters as Management Zones) into a Kubernetes control plane, and VKS clusters (Cluster API, built-in ClusterClass) are the conformant workload clusters it provisions. VCF Automation All Apps organizations consume Supervisors through Regions, Zones and vSphere Namespaces.

Supervisor topology (VCF 9.0.1 — Requirements for Supervisor Deployment with VPC Networking; Change the Control Plane Size)

ElementWhat it is
Control plane VMsOne VM (single Management Zone, the default when the Supervisor is activated during workload-domain creation) or three VMs (three Management Zones / HA). Sizes: Tiny 2 CPU / 8 GB, Small 4 CPU / 16 GB (default), Medium 8 CPU / 16 GB, Large 16 CPU / 32 GB, 32 GB disk each; the size can only be scaled up. The minimum-requirements table lists 4 CPU / 16 GB per control plane VM.
ESX hostsMembers of the Supervisor's cluster(s); Spherelet runs on each host so it can run vSphere Pods and host VKS cluster node VMs. vSphere DRS (Fully Automated) and vSphere HA must be enabled.
Supervisor servicesKubernetes operators installed and managed per Supervisor. The Velero vSphere Operator is a core Supervisor Service: it comes pre-registered with vCenter but is installed on each Supervisor as a separate step (Supervisor Management > Services). Further Supervisor Services (Harbor, external-dns, Contour and others) are added from the service catalog.
vSphere NamespacesLogical pools of CPU, memory and storage from one to three Zones; created per project from Namespace Classes; carry storage classes, VM classes, content libraries and quotas.
Regions and ZonesA Region is a set of Supervisors sharing an NSX Local Manager; Zones are vSphere clusters supplying compute; the provider assigns them to organizations through Region Quotas.

Networking stacks for the Supervisor (VCF 9.0 — Supervisor networking; Deprecation Announcements)

StackLoad balancingNotes
VCF Networking with NSX VPCNSX load balancer (and Avi where configured)Default when the Supervisor is activated from VCF Operations; per-namespace VPC multi-tenancy; required to unlock the full 9.0 capability set; VKS 3.3.1 or later for VPC networks
NSX Tier-0 / Tier-1 segmentsNSX load balancerThe pre-9.0 NSX model; still supported
VDS networkingFoundation Load Balancer (bundled with vCenter, Layer 4, VLAN-backed topologies, VDS only) or Avi Load BalancerHAProxy is deprecated in VCF 9.0 (to be removed in a future major release)

vSphere Pods are only supported with NSX-based networking.

Kubernetes releases (VCF 9.0 — VKS 3.3.1 what's new)

  • Node images are VKr (VMware Kubernetes release) images delivered through a subscribed or local content library; the TKR name belongs to the Tanzu era.
  • VKS 3.3.1 on VCF 9.0 adds VKr 1.32 and drops VKr 1.27.x (and 1.31.1, adding 1.31.4); to upgrade to VKS 3.3.0 or later, every cluster must already run VKr 1.28 or later. Later VKS releases raise the floor again (see the VCF 9.0 → 9.1 delta section for VKS 3.6).
  • A VKS cluster pins its release in spec.topology.version (for example v1.32.0---vmware.6-fips-vkr.2); upgrades change that field.

Key design facts

  • Supervisor and VKS cluster are different constructs: workloads run in VKS clusters (VMs) or as vSphere Pods on the Supervisor; neither runs 'on TKG worker nodes by default'.
  • The Supervisor control plane is HA with three VMs across three hosts (or three Zones); one VM means a single point of failure and vSphere HA restart as the recovery.
  • Isolation layers available to a design: vSphere Namespace (quota, RBAC, storage and VM classes), NSX VPC per namespace (network), Antrea NetworkPolicy / ClusterNetworkPolicy inside clusters, Pod Security Admission, and separate Supervisors or Zones for hard tenancy.

Key Takeaways

  • Supervisor control plane: 1 or 3 VMs sized Tiny/Small/Medium/Large (2/4/8/16 CPU; 8/16/16/32 GB; Small default; scale-up only), DRS Fully Automated and HA required; Spherelet on every ESX host.
  • Networking choices in 9.0: NSX VPC (default from VCF Operations, full capability set), NSX Tier-0/Tier-1 segments, or VDS with Foundation Load Balancer (L4, VLAN) or Avi; HAProxy is deprecated; vSphere Pods need NSX.
  • Images are VKr (not TKR): VKS 3.3.1 supports VKr 1.28–1.32 on VCF 9.0; a VKS cluster pins its release in spec.topology.version and upgrades by changing it.

Supervisor Cluster Setup & Configuration#

Supervisor activation in VCF 9.0 happens from VCF Operations during workload-domain creation (optional step, VCF Networking with VPC by default) or later from the vSphere Client (Workload Management).

Prerequisites (VCF 9.0.1 — Requirements for Supervisor Deployment with VPC Networking)

ItemRequirement
vSphere clusters1 or 3 clusters (three for three Management Zones); DRS Fully Automated and HA enabled on each
ESX hosts per clusterWithout vSAN: 1 host (3 recommended); with vSAN: 3 hosts (4 recommended); each host 8 CPU and 64 GB RAM; host names in lower case
vCenter 9.0Small or larger (2 CPU / 21 GB / 290 GB minimum)
NSX ManagerMedium (6 CPU / 24 GB / 300 GB)
NSX Edge clusterTwo Large nodes (8 CPU / 32 GB / 200 GB) in Active/Standby for load balancing and NAT
Control plane VMs1 (single Zone) or 3 (three Zones); 4 CPU / 16 GB / 16 GB each at minimum size
NetworksESX TEP network; Edge TEP network (may share the ESX TEP VLAN); Tier-0 uplink network and a block of 5 uplink IPs; TEP MTU greater than 1600; management network for the control plane VMs (default ESX management network or a dedicated port group / VPC subnet); no IPv6 clusters with a 9.0 Supervisor
StorageStorage policies for control plane VMs, ephemeral disks and image cache; vSAN optional
Content librarySubscribed (internet) or local (air-gapped) library holding the VKr images

Activation flow (VPC networking)

  1. Deploy the NSX Edge cluster and set up the Tier-0 connectivity in the workload domain; create the VPC constructs in vCenter.
  2. If not using the default ESX management network, configure the port groups or VPC subnets for the Supervisor management network.
  3. Configure the Centralized Gateway.
  4. Optionally deploy and configure Avi Load Balancer.
  5. Activate the Supervisor (from VCF Operations at domain creation, or Workload Management in the vSphere Client): choose single or three Zones, control plane size, management network, storage policies and the content library.
  6. Create vSphere Namespaces (or let VCF Automation create them from Namespace Classes), assign users/groups, storage classes, VM classes and quotas.

Alternative stacks

  • VDS networking with Foundation Load Balancer: Layer 4 only, VLAN-backed topologies, bundled with vCenter; chosen for simple or lab Supervisors. Avi Load Balancer is the fuller VDS option (L4/L7, GSLB).
  • NSX Tier-0/Tier-1 segments: the pre-VPC NSX model, still supported for existing designs.

Operational checks after activation

  • Supervisor status Running in Workload Management; control plane VMs on separate hosts/Zones; Kubernetes API reachable on the Supervisor virtual IP.
  • Content library synced (VKr images visible as kubectl get kubernetesreleases / VCF CLI vcf kubernetes-release get in a namespace context).
  • Namespace created with at least one storage class and VM class before the first VKS cluster request.

Lab note (Holodeck): the nested site's Supervisor can be activated with VPC networking on the workload domain cluster; use the Holodeck documented default sizes and expect single-Zone, one control plane VM in the nested footprint.

Key Takeaways

  • VCF 9.0 Supervisor minimums: 1 host without vSAN (3 recommended) or 3 with vSAN (4 recommended), 8 CPU / 64 GB per host, DRS Fully Automated + HA, vCenter 9.0 Small, NSX Manager Medium, two Large Edge nodes, TEP MTU > 1600, no IPv6 clusters.
  • Activation from VCF Operations at workload-domain creation uses VCF Networking with VPC by default; from the vSphere Client you choose the stack (NSX VPC, NSX segments, VDS + Foundation LB / Avi) and single vs three Management Zones.
  • Validate before the first cluster: Supervisor Running, control plane VMs spread, content library synced with VKr images, namespace with storage class and VM class.

TKG Cluster Lifecycle: Provisioning to Upgrade#

VKS clusters are Cluster API clusters provisioned from a vSphere Namespace using the built-in ClusterClass. The legacy TanzuKubernetesCluster (TKC) API is deprecated in favour of the v1beta1 Cluster API.

Cluster manifest (VCF 9.0.1 — VKS cluster v1beta1 example, trimmed)

apiVersion: cluster.x-k8s.io/v1beta1
kind: Cluster
metadata:
  name: prod-cluster-01
  namespace: ns-prod
spec:
  clusterNetwork:
    pods:
      cidrBlocks: ["192.168.156.0/20"]
    services:
      cidrBlocks: ["10.96.0.0/12"]
    serviceDomain: cluster.local
  topology:
    class: builtin-generic-v3.3.0
    version: v1.32.0---vmware.6-fips-vkr.2
    variables:
      - name: vmClass
        value: best-effort-medium
      - name: storageClass
        value: <storage-policy-name>
    controlPlane:
      replicas: 3
    workers:
      machineDeployments:
        - class: node-pool
          name: np-general
          replicas: 3
          metadata:
            annotations:
              cluster.x-k8s.io/cluster-api-autoscaler-node-group-min-size: "3"
              cluster.x-k8s.io/cluster-api-autoscaler-node-group-max-size: "8"
  • class is the built-in ClusterClass shipped with the Supervisor release (for example builtin-generic-v3.3.0); 'tanzukubernetescluster' is not a ClusterClass.
  • version is the VKr string from the content library; variables carry the vmClass and storageClass (and optional extras such as node labels, volumes, proxy, trust bundles).
  • Control plane replicas 1 or 3; MachineDeployments are generated from the topology — scale or edit the Cluster object, not the MachineDeployment.

Lifecycle operations

OperationHow
Createkubectl apply -f cluster.yaml in the namespace context (kubectl with the vSphere plug-in, or VCF CLI vcf context + vcf cluster create), or through VCF Automation (CCI.Supervisor.Resource) / Terraform
ScaleChange replicas in the worker pool (or let the Cluster Autoscaler do it)
AutoscaleInstall the Cluster Autoscaler standard package on the workload cluster, then set the min-size / max-size annotations on the worker pool; from VKr 1.31.4 scaling from and to zero is supported
UpgradeChange spec.topology.version to a newer VKr (one minor at a time); control plane nodes roll first, then worker pools; respect PodDisruptionBudgets
PackagesStandard packages (Cluster Autoscaler, Velero, Harbor, external-dns, Contour, cert-manager, Fluent Bit, Prometheus/Grafana and others) from the package repository, installed with the VCF CLI package plug-in on the workload cluster
BackupVelero standard package on the workload cluster (installing Velero through the Velero operator is deprecated); Kopia replaces Restic for file-system backups from Velero 1.15 (Restic restores end with 1.19)
SnapshotsCluster-level snapshots of VKS clusters as documented for the release; volume snapshots via the vSphere CSI driver

Velero example (Schedule, not Backup, carries the cron expression)

apiVersion: velero.io/v1
kind: Schedule
metadata:
  name: nightly
  namespace: velero
spec:
  schedule: "0 2 * * *"
  template:
    includedNamespaces: ["production", "staging"]
    excludedNamespaces: ["kube-system", "kube-public"]
    storageLocation: s3-backup-bucket
    ttl: 720h

Velero backs up Kubernetes API objects and volume data through the Kubernetes API and CSI snapshots; it is not an etcd snapshot. The Supervisor's own control plane is protected by vSphere HA and the Velero Supervisor Service.

Design guidance

  • One namespace per team or tenant with quota, storage classes and VM classes sized to the workload; several small clusters are easier to upgrade than one large one.
  • Pin VKr versions deliberately and plan the upgrade cadence against the VKS compatibility window (1.28–1.32 on VCF 9.0 with VKS 3.3.1).
  • Document autoscaler bounds, PDBs and the backup target per cluster class (dev/prod).

Key Takeaways

  • VKS clusters are Cluster API v1beta1 objects with the built-in ClusterClass (builtin-generic-v3.3.0), a VKr version string and vmClass/storageClass variables; TKC is deprecated; scale and upgrade by editing the Cluster, not the MachineDeployment.
  • Autoscaling = Cluster Autoscaler standard package + min/max-size annotations on the worker pool (scale to/from zero from VKr 1.31.4); packages are installed with the VCF CLI package plug-in.
  • Backup with the Velero standard package (operator install deprecated; Kopia replaces Restic): a Schedule carries the cron expression and a template, Backup objects do not.

Supervisor Architecture Deep Dive#

Supervisor internals for the exam and the design defence (VCF 9.0.1 — Supervisor concepts; vSphere Pods)

Control plane availability

  • A three-VM Supervisor control plane is a stacked Kubernetes control plane: each VM runs kube-apiserver, etcd, controller-manager and scheduler. All three API servers serve requests behind the Supervisor virtual IP; etcd elects one leader and keeps quorum while two of three members are up, so one VM failure is tolerated; the scheduler and controller-manager use leader election among the three. The VCF docs describe three VMs running two instances of most controllers.
  • A one-VM Supervisor (single Management Zone default, or 'single host' Supervisor with vSphere HA deactivated) has no quorum protection; recovery is a vSphere HA restart or a manual rebuild. Scaling from one to three control plane VMs is a supported day-2 change; sizes only scale up.
  • Control plane VMs are system-managed VMs (not pods) placed on separate hosts (anti-affinity) or separate Zones.

vSphere Pods

  • A vSphere Pod is a VM with a small footprint that runs one or more Linux containers, managed by the Spherelet on the ESX host and run by the CRX runtime with its own Photon-based Linux kernel. Each pod is sized precisely for its workload with explicit reservations; DRS places it; it gets VM-level isolation while keeping container-like start-up time and overhead; OCI images run unchanged.
  • vSphere Pods are only supported when the Supervisor uses NSX networking. They are an alternative to VKS cluster nodes for small, isolated services, not the default location of Supervisor workloads.
  • The Kata containers comparison is not the VCF mechanism; do not cite it.

Networking inside the platform

  • Supervisor with NSX: per-namespace Tier-1 or VPC, segments/subnets, SNAT and load-balancer VIPs created by the Supervisor's NSX integration (the NCP-based integration in the Supervisor).
  • VKS clusters: Antrea (default) or Calico is the CNI (Table 1598), and the CNI enforces Kubernetes NetworkPolicy inside the cluster. Antrea–NSX integration applies to Antrea clusters: the Antrea NSX Adapter synchronises the cluster's Kubernetes network policies into the NSX inventory, where they cannot be edited (a one-way import through the NSX API converts them to vDefend DFW policies); DFW policies that NSX applies to an Antrea cluster are enforced by that cluster's Antrea Controller; and Antrea Traceflow can be started from NSX Manager.
  • Ingress and services: NSX load balancer, Avi, or Foundation Load Balancer depending on the stack; Contour as an in-cluster ingress package.

Identity and access

  • Supervisor access through vCenter SSO (and VCF SSO) with kubectl vsphere login, or through external OIDC identity providers configured on the Supervisor (Pinniped) so VKS clusters accept enterprise identities; VCF CLI contexts wrap the same login.
  • Namespace permissions (view/edit/owner) are granted to users or groups per namespace; in All Apps organizations VCF Automation project roles map onto them.

Multi-tenancy design checklist

LayerControl
Compute/storagevSphere Namespace quotas, VM classes, storage classes; Zones for failure domains
NetworkNSX VPC per namespace; Antrea/NSX policies in clusters; Avi or NSX LB per tenant VIP range
PlatformPod Security Admission levels per namespace; RBAC; separate Supervisors or Zones for hard isolation
LifecycleVKr version policy, upgrade windows per cluster class, Velero backup per tenant

Troubleshooting pointers

  • Supervisor activation stalls: check the Workload Management configuration status messages, DNS and NTP for the control plane VMs, content library sync, Edge cluster and Tier-0 health, TEP MTU (> 1600), and that host names are lower case.
  • VKS cluster stuck Provisioning: kubectl get cluster,machines -n <ns> and kubectl describe the Machine; usual causes are an exhausted IP pool, a VM class or storage class not assigned to the namespace, a content library without the requested VKr, or quota exhaustion.
  • Pods pending: node resources vs requests, storage class availability, Antrea agent health; for vSphere Pods confirm the Supervisor runs NSX networking.

Key Takeaways

  • HA control plane = three stacked control plane VMs; all three API servers serve behind the VIP, etcd quorum tolerates one failure, scheduler/controller-manager use leader election; one VM means vSphere HA restart is the recovery.
  • vSphere Pods are small-footprint VMs run by Spherelet/CRX with their own kernel, DRS-placed, NSX networking only; VKS cluster nodes are separate VMs with Antrea (default) or Calico as CNI (Antrea–NSX integration shows the cluster's Kubernetes policies in NSX read-only, and DFW policies that NSX applies to the cluster are enforced by its Antrea Controller).
  • Troubleshoot from the object chain: Workload Management status → Cluster/Machine objects → namespace VM class, storage class, content library and IP pool; verify TEP MTU > 1600 and lower-case host names at activation.

Exam Mapping: 3V0-24.25 — Advanced VCF 9.0 VKS (vSphere Kubernetes Service)

  • Supervisor architecture, networking stacks (NSX VPC, NSX segments, VDS, Avi, Foundation Load Balancer), identity providers, content libraries including air-gapped
  • VKS cluster lifecycle: Cluster API/ClusterClass, VKr versions, scaling and autoscalers, standard packages and package repositories, snapshots, Supervisor Service upgrades, kubectl and VCF CLI
  • Multi-tenancy and security: namespaces, quotas, NSX VPC isolation, Antrea/NSX policies, Pod Security Admission, RBAC, service mesh
  • Troubleshooting Supervisor activation, cluster provisioning, networking and storage
  • Note: VCDX Academy study groupings; the official 3V0-24.25 exam guide (docs.broadcom.com, 'VMware VCAP VKS exam guide') is the authority for objectives and must be cross-checked

Labs in This Section

📝 Quiz — VCAP Advanced VKS

0/50 correct

Architecture

Q1
Which three layers describe the VKS stack from bottom up?
  • VKS Cluster → Supervisor → Namespace
  • Supervisor → vSphere Namespace → VKS Cluster
  • Namespace → Supervisor → VKS Cluster
  • vCenter → Supervisor → Pods
VKS stack bottom-up: Supervisor (vSphere integration layer) → vSphere Namespace (isolation boundary) → VKS Cluster (workload Kubernetes cluster). Namespace before Supervisor is wrong. VKS Cluster isn't at the bottom. vCenter isn't part of the VKS stack directly.
Q2
Spherelet is best described as:
  • A monitoring agent inside guest VMs
  • A Kubernetes controller running on ESXi hosts integrating Pod lifecycle with the hypervisor
  • An NSX Edge service
  • A CNI plugin for Linux
Spherelet is a Kubernetes controller running on ESXi hosts that integrates Pod lifecycle with the hypervisor, enabling vSphere Pods. It's not a CNI plugin, monitoring agent, or NSX Edge service.
Q3
A production Supervisor requires HA for the control plane. How many Control Plane VMs are deployed?
  • Two with a witness
  • Three (in an HA set)
  • One
  • Five
Production Supervisors deploy three Control Plane VMs in an HA set for etcd quorum. One provides no redundancy. Five is over-provisioned. Two with witness doesn't match Kubernetes HA patterns.
Q4
Which networking backing uses NSX segments with dedicated T1 per namespace?
  • Antrea-only backing
  • VDS-backed Supervisor
  • Host-only networking
  • NSX-backed Supervisor
NSX-backed Supervisor provides NSX segments with a dedicated Tier-1 gateway per namespace, enabling overlay networking with full NSX security. VDS-backed uses distributed port groups. Antrea-only and host-only are not Supervisor backing options.
Q5
CAPV (Cluster API Provider vSphere) is responsible for:
  • Managing VKS cluster lifecycle via Cluster API CRDs on vSphere
  • DNS resolution inside pods
  • Running Harbor
  • Container image scanning
CAPV (Cluster API Provider vSphere) manages VKS cluster lifecycle via Cluster API CRDs, handling VM provisioning, scaling, and upgrades on vSphere. It doesn't scan images, run Harbor, or handle DNS resolution.

Cluster Lifecycle

Networking

Storage

Security and Operations

🃏 Flashcards — VCAP Advanced VKS

50 cards
Card 1 of 50
Supervisor Cluster
The vSphere cluster where VKS is enabled, with its Control Plane VMs running Kubernetes APIs and its ESXi hosts running Spherelet. It hosts vSphere Pods and manages downstream VKS guest clusters. It is the foundational layer of the three-layer VKS architecture.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.