In this post, I will help you to know , how to add Tanzu Kubernetes Grid management cluster with Tanzu mission control
Adding Tanzu Kubernetes Grid management clusters with Tanzu Mission Control allow you to provision and manage Tanzu Kubernetes clusters by using the Tanzu Mission Control dashboard.
Before registering your Tanzu Kubernetes Grid management cluster with Tanzu Mission Control must be meet below prerequires.
- You must be a member of VMware Cloud Services organization that has access to Tanzu Mission Control. For more information,
- Management clusters that you register in Tanzu Mission Control must be production clusters with multiple control plane nodes. This configuration allows Tanzu Mission Control to support complete lifecycle management for Tanzu Kubernetes clusters that are managed by the management cluster. For more information.
you can only register Tanzu Kubernetes Grid management clusters that are deployed on certain infrastructure providers. Below are the list of currently supported . providers.
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 .
- Tanzu Kubernetes Grid management clusters (version 1.3.1 or 1.4.1) running in Microsoft Azure.
- Tanzu Kubernetes Grid management clusters (version 1.4.1) running in Amazon Web Services (AWS).
- Tanzu Kubernetes Grid management clusters (version 1.3) 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).
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.
When you add workload clusters, you can choose the cluster group into which to place them. This setting simply indicates the default choice.
When you add workload clusters, you can choose which proxy configuration to use. This setting simply indicates the default choice.
When you click , generates a YAML file that defines how the management cluster connects to for registration. The credential provided in the YAML expires after 48 hours. You can optionally click View YAML to see the code.
For clusters running in or , this is typically the vSphere administrator.