To understand the licensing, you must understand the architecture:
vSphere Kubernetes licensing follows the same metric as traditional vSphere: . vsphere kubernetes license
do not include native Kubernetes services. Kubernetes features for these versions must be accessed through the newer VVF or VCF bundles. VMware +3 Key Licensing Metrics (2026) Feature VCF / VVF Policy Metric Per-Core licensing (minimum of 16 cores per physical CPU). Model Subscription only (1, 3, or 5-year terms). Reporting Active monitoring and telemetry; usage is reported directly to the VMware Cloud Console. Add-ons Tanzu Mission Control (TMC) and advanced Tanzu services are typically sold as To understand the licensing, you must understand the
If you are on an older version of vSphere (6.7 or early 7.0) or haven't migrated to the Broadcom subscription model: VMware +3 Key Licensing Metrics (2026) Feature VCF
If you have vSphere Standard, you have the platform foundation, but you lack the license rights to spin up the multi-node Kubernetes clusters that most development teams require.
To enable the native "Workload Management" features within vCenter, you generally need a specific edition of vSphere or a Tanzu-specific add-on: