Configuring and Managing a Supervisor Cluster

You use the Clusters service to enable and disable a Supervisor Cluster, or edit the configuration of an existing Supervisor Cluster. The Clusters service is provided within the namespace_management package.

You can enable a vSphere cluster to manage Kubernetes workload objects, only after you enable vSphere DRS in fully automated mode and enable HA on the cluster.

Before you enable programmatically a vSphere with Tanzu on a vSphere cluster, you must prepare your environment to meet the specific networking, storage, and infrastructure requirements. See the vSphere with Tanzu Configuration and Management documentation.

For more information about how to configure the storage settings to meet the requirements of vSphere with Tanzu, see Creating Storage Policies for vSphere with Tanzu.

For more information about how to configure the networking settings for Supervisor Clusters that are configured with the VMware NSX-T™ Data Center as the networking stack, see Configuring NSX-T Data Center for vSphere with Tanzu.

Starting with vSphere 7.0 Update 1, you can enable a Supervisor Cluster with vSphere networking or NSX-T Data Center, to provide connectivity between control planes, services, and workloads. A Supervisor Cluster that is configured with vSphere networking uses a vSphere Distributed Switch to provide connectivity to Kubernetes workloads and control planes. The cluster also requires a third-party load balancer that provides connectivity to DevOps users and external services. You can install in your vSphere environment the HAProxy load balancer implementation that VMware provides. See Configuring the vSphere Networking Stack for vSphere with Tanzu and Installing and Configuring the HAProxy Load Balancer.