A customer is implementing a new VMware Cloud Foundation (VCF) instance and has a requirement to deploy Kubernetes-based applications. The customer…

The customer requires Kubernetes-based application deployment within a new VCF 5.2 instance

without additional licensing costs. VCF includes foundational components and optional features,

some requiring separate licenses. Let’s evaluate each option:

Option A: Tanzu Mission Control

Tanzu Mission Control (TMC) is a centralized management platform for Kubernetes clusters across

environments. It’s a SaaS offering requiring a separate subscription, not included in the base VCF

license. The VCF 5.2 Architectural Guide excludes TMC from standard VCF features, making it

incompatible with the no-budget constraint.

Option B: VCF Edge

VCF Edge refers to edge computing deployments (e.g., remote sites) using lightweight VCF instances.

It’s not a Kubernetes-specific feature and doesn’t inherently provide Kubernetes capabilities without

additional configuration or licensing (e.g., Tanzu). The VCF 5.2 Administration Guide positions VCF

Edge as an architecture, not a Kubernetes solution.

Option C: Aria Automation

Aria Automation (formerly vRealize Automation) provides cloud management and orchestration,

including some Kubernetes integration via Tanzu Service Mesh or custom workflows. However, it’s an

optional component in VCF, often requiring additional licensing beyond the base VCF bundle, per the

VCF 5.2 Licensing Guide. It’s not mandatory for basic Kubernetes and violates the budget restriction.

Option D: IaaS control plane

In VCF 5.2, the IaaS control plane includes VMware Cloud Director or the native vSphere with Tanzu

capability (via NSX and vSphere 7.x). vSphere with Tanzu, enabled through the Workload

Management feature, provides a Supervisor Cluster for Kubernetes without additional licensing

beyond VCF’s core components (vSphere, vSAN, NSX). The VCF 5.2 Architectural Guide confirms that

vSphere with Tanzu is included in VCF editions supporting NSX, allowing Kubernetes-based

application deployment (e.g., Tanzu Kubernetes Grid clusters) at no extra cost.

Conclusion:

The IaaS control plane (D), leveraging vSphere with Tanzu, meets the requirement for Kubernetes

deployment within VCF 5.2’s existing licensing, satisfying the no-budget constraint.

Reference:

VMware Cloud Foundation 5.2 Architectural Guide (docs.vmware.com): IaaS Control Plane and

vSphere with Tanzu.

VMware Cloud Foundation 5.2 Administration Guide (docs.vmware.com): Workload Management

Features.

VMware Cloud Foundation 5.2 Licensing Guide (docs.vmware.com): Included Components.