vSphere with Tanzu requires specific networking configuration to enable connectivity to the Supervisor Clusters, Supervisor Namespaces, and all objects that run inside the namespaces, such as vSphere Pods and Tanzu Kubernetes clusters. As a vSphere administrator, install and configure NSX-T Data Center for vSphere with Tanzu.

The Supervisor Cluster uses an opinionated networking configuration. Two methods exist to configure the Supervisor Cluster networking that result in deploying the same networking model:
  • The simplest way to configure the Supervisor Cluster networking is by using the VMware Cloud Foundation SDDC Manager. For more information, see the VMware Cloud Foundation SDDC Manager documentation. For more information, see Working with Workload Management.
  • You can also configure the Supervisor Cluster networking manually by using an existing NSX-T Data Center deployment or by deploying a new instance of NSX-T Data Center.

This section describes how to configure the Supervisor Cluster networking by deploying a new NSX-T Data Center instance, but the procedures are applicable against an existing NSX-T Data Center deployment as well. This section also provides background to understand what VMware Cloud Foundation SDDC Manager is doing when it sets up the Supervisor Cluster workload domain.

Prerequisites

  • Verify that your environment meets the system requirements for configuring a vSphere cluster as a Supervisor Cluster. For information about requirements, see System Requirements and Topologies for Setting Up a Supervisor Cluster with NSX-T Data Center.
  • Assign the VMware vSphere 7 Enterprise Plus with Add-on for Kubernetes license to all ESXi hosts that will be part of the Supervisor Cluster.
  • Create storage policies for the placement of control plane VMs, pod ephemeral disks, and container images.
  • Configure shared storage for the cluster. Shared storage is required for vSphere DRS, HA, and storing persistent volumes of containers.
  • Verify that DRS and HA is enabled on the vSphere cluster, and DRS is in the fully automated mode.
  • Verify that you have the Modify cluster-wide configuration privilege on the cluster.