Learn about the minimum requirements for Tanzu Kubernetes clusters that you manage through VMware Tanzu Mission Control and the platforms that are supported for this integration.

Configuration Requirements for Registering Tanzu Kubernetes Clusters

To effectively use Tanzu Mission Control to manage your Tanzu Kubernetes clusters, make sure that your clusters abide by the following configuration guidelines.
  • Your Tanzu Kubernetes Grid management cluster must be a production cluster with multiple control plane nodes.
  • Tanzu Kubernetes Grid workload clusters need at least 4 CPUs and 8 GB of memory.
  • To add a Tanzu Kubernetes Grid workload cluster to Tanzu Observability, the cluster must have a minimum of two worker nodes.

Supported Environments for Registering Tanzu Kubernetes Clusters

Tanzu Mission Control supports the registration of management clusters running in the following environments:
  • Tanzu Kubernetes Grid Service Supervisor Clusters running in vSphere with Tanzu or running in VMware Cloud with Tanzu services.
  • Tanzu Kubernetes Grid management clusters (version 1.3.1 or 1.4.1 or later) running in Microsoft Azure.
  • Tanzu Kubernetes Grid management clusters (version 1.4.1 or later) running in Amazon Web Services (AWS).
  • Tanzu Kubernetes Grid management clusters (version 1.3 or later) running in vSphere on Azure VMware Solution (AVS).
  • Tanzu Kubernetes Grid management clusters (version 1.2 or later) running in vSphere, including vSphere on VMware Cloud on AWS (version 1.12 or 1.14 or 1.16 or 1.18 or 1.20).

Do not attempt to register any other kind of management cluster with Tanzu Mission Control.

  • Tanzu Mission Control does not support the registration of Tanzu Kubernetes Grid management clusters prior to version 1.2.

CNI requirement for managing the lifecycle of a workload cluster

After you register a management cluster with Tanzu Mission Control, you can manage the lifecycle of workload clusters (create, upgrade, and delete) in that management cluster.

The Antrea CNI (container network interface) is required for cluster lifecycle management through Tanzu Mission Control. Although you can manage clusters that use an alternative CNI, such as Calico, you will not be able to upgrade the Kubernetes version on that cluster. If you intend to manage the lifecycle of a workload cluster through Tanzu Mission Control, make sure the cluster is created using the Antrea CNI.