Check out the prerequisites for enabling vSphere with Tanzu in your vSphere environment. To run container-based workloads natively on vSphere, as a vSphere administrator you enable Workload Management on a vSphere cluster. The result is a Kubernetes management cluster known as a Supervisor Cluster where you run vSphere Pods, provision Tanzu Kubernetes clusters, and VMs.

Create and Configure a vSphere Cluster

A vSphere cluster is a collection of ESXi hosts managed by a vCenter Server system. The Supervisor Cluster runs on a vSphere cluster. Create a vSphere cluster that meets the following requirements so that you can enable Workload Management on it:

Caution: Do not disable vSphere DRS after you configure the Supervisor Cluster. Having DRS enabled at all times is a mandatory prerequisite for running workloads on the Supervisor Cluster. Disabling DRS leads to breaking your Tanzu Kubernetes clusters.

Choose and Configure the Networking Stack

To enable Workload Management on a vSphere cluster, you must configure the networking stack to be used for the Supervisor Cluster. You have two options: NSX or vSphere Distributed Switch (vDS) networking with a load balancer. You can configure the NSX Advanced Load Balancer or the HAProxy load balancer.

The table lists the high-level differences between the two supported networking stacks. For more information about the architectural differences, see Supervisor Cluster Configured with the vSphere Networking Stack.
Functionality NSX-T Networking vDS Networking
vSphere Pods Yes No
Tanzu Kubernetes clusters Yes Yes
Embedded Harbor Registry Yes No
Load Balancing Yes Yes, by installing and configuring the NSX Advanced Load Balancer or the HAProxy load balancer.
To use NSX networking for the Supervisor Cluster:
To use vSphere vDS networking with the NSX Advanced Load Balancer for the Supervisor Cluster:
Note: vSphere with Tanzu supports the NSX Advanced Load Balancer with vSphere 7 U2 and later.
To use vSphere vDS networking with HAProxy load balancing for the Supervisor Cluster:
Note: vSphere with Tanzu supports the HAProxy load balancer with vSphere 7 U1 and later.

Create Storage Policy

You must create storage policies that will determine the datastore placement of the Kubernetes control plane VMs, containers, and images. You can create storage policies associated with different storage classes.

Before enabling Workload Management on a vSphere cluster, create a storage policy for the placement of Kubernetes control plane VMs. See Create Storage Policies for vSphere with Tanzu.

Create a Content Library

To provision Tanzu Kubernetes clusters and VMs, you need a Content Library created in the vCenter Server that manages the vSphere cluster where the Supervisor Cluster runs.

The Content Library provides the system with the distributions of Tanzu Kubernetes releases in the form of OVA templates. When you provision a Tanzu Kubernetes cluster, the OVA template for the selected version is used to create the Kubernetes cluster nodes.

You can create a Subscribed Content Library to automatically pull the latest released images, or you can create a Local Content Library and manually upload the images, which may be required for air-gapped provisioning of Tanzu Kubernetes clusters.

See Creating and Managing Content Libraries for Tanzu Kubernetes releases.

Watch vSphere with Tanzu Demos

Although not a hard requirement, before you embark it may be helpful to watch some demonstrations of vSphere with Tanzu, including setting up the vSphere environment in preparation for deploying the Supervisor Cluster, enabling Workload Management, and provisioning Tanzu Kubernetes clusters. If this sounds useful, check out the series of vSphere with Tanzu Deep Dive videos on the VMware vSphere channel. You can also check the vSphere Tanzu Quick Bytes series of short videos for configuring Workload Management with vDS networking and HAProxy Load Balancer.