You can start using vSphere with Tanzu with NSX-T Data Center networking on a cluster that uses a single vSphere Lifecycle Manager image by enabling the cluster for Workload Management. A cluster enabled with Workload Management is called a Supervisor Cluster. You enable the cluster for Workload Management from the Workload Management user interface in the vSphere Client. Upon enabling Workload Management on a Supervisor Cluster configured with the NSX-T networking stack, vSphere Lifecycle Manager installs the Spherelet VIB on every ESXi host in the cluster.
- Verify that all ESXi hosts in the Supervisor Cluster are version 7.0 Update 2 or later.
- Verify that all ESXi hosts in the Supervisor Cluster are assigned the VMware vSphere 7 Enterprise Plus with Add-on for Kubernetes license.
- Verify that vCenter Server is version 7.0 Update 2 or later.
- Review the configuration requirements and additional information in "Working with vSphere Lifecycle Manager" chapter in the vSphere with Tanzu documentation.
- You can upgrade a Supervisor Cluster to the latest version of vSphere with Tanzu. You can also upgrade the ESXi version of the hosts in the Supervisor Cluster.
You perform the upgrade of the Supervisor Cluster from the Workload Management user interface in the vSphere Client. During upgrade, vSphere Lifecycle Manager upgrades the Spherelet VIB on the hosts to make it compatible with the new version of vSphere with Tanzu or the new version of ESXi.
You upgrade the ESXi version of the hosts in the Supervisor Cluster by remediating the cluster from the vSphere Lifecycle Manager user interface in the vSphere Client.Note: You cannot perform a simultaneous upgrade of both vSphere with Tanzu and ESXi.
- You deactivate vSphere with Tanzu from the Workload Management user interface in the vSphere Client.You can deactivate vSphere with Tanzu on a cluster that uses a single vSphere Lifecycle Manager image.
When you deactivate vSphere with Tanzu, you can use the cluster for traditional virtual machine workloads.
- You can add and remove hosts to and from a Supervisor Cluster that uses vSphere Lifecycle Manager images.
When you add a host to a Supervisor Cluster that you manage with a single vSphere Lifecycle Manager image, vSphere Lifecycle Manager automatically installs the Spherelet VIB on the newly added host.
When you remove a host from a Supervisor Cluster that you manage with a single vSphere Lifecycle Manager image, vSphere Lifecycle Manager removes the Spherelet VIB from the host. vSphere Lifecycle Manager also deletes the Spherelet VIB from a host that you move to another Supervisor Cluster.
For more information about adding and removing hosts to and from a cluster, see the vCenter Server and Host Management documentation.
For detailed information about working with a Supervisor Cluster that uses a single image, see the "Managing a Supervisor Cluster Using vSphere Lifecycle Manager" section in the vSphere with Tanzu documentation.
Upgrading the vSphere with Tanzu Components in a vSAN Cluster
To upgrade the vSphere with Tanzu components installed on the hosts in a cluster, you must remediate the cluster against a vSphere Lifecycle Manager image that contains the latest version of those vSphere with Tanzu components.
In a vSAN cluster with configured fault domains, vSphere Lifecycle Manager recognizes the configured fault domains for the cluster and performs the solution upgrade in accordance with the fault domain configuration. If the vSAN cluster is a stretched cluster, you must upgrade the witness host separately, after vSphere Lifecycle Manager finishes remediating all fault domains. For more information about remediating vSAN stretched clusters and vSAN clusters configured with fault domains, see Using vSphere Lifecycle Manager Images to Remediate vSAN Clusters with Configured Fault Domains. For more information about stretched clusters, see the vSAN Planning and Deployment documentation.
For information about the scalability that vSphere Lifecycle Manager supports, visit the VMware Configuration Maximums Matrix at https://configmax.vmware.com/.