Search This Blog

Tuesday, February 22, 2022

Add Tanzu Kubernetes Grid management cluster with Tanzu mission control

 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.


Before deploying your management cluster on AWS, ensure that the tkg-cloud-vmware-com CloudFormation stack in the target AWS account includes the IAM permissions listed in Permissions Required by Tanzu Mission Control. These permissions are included automatically when you create or update the CloudFormation stack by running the tanzu management-cluster permissions aws set command.

If you configured the IAM permissions defined in the CloudFormation stack manually, you must add the permissions listed in Permissions Required by Tanzu Mission Control to the IAM policy or role.



After you have deployed your management cluster through the Tanzu Kubernetes Grid installer interface or the Tanzu CLI, follow these instructions in the Tanzu Mission Control .


1.     In the Tanzu Mission Control console, click Administration in the left navigation pane.

2.     Click the Management clusters tab.

3.     Click Register Management Cluster, and then choose the kind of cluster you are registering.

4.     On the Register page, provide a name for the management cluster, and select a default cluster group for workload clusters.

When you add workload clusters, you can choose the cluster group into which to place them. This setting simply indicates the default choice.

5.     You can optionally provide a description and labels for the management cluster.

6.     Click Next.

7.     You can optionally select a proxy configuration for the cluster.

a.     Click to toggle the Set proxy option to Yes.

b.     Select the proxy configuration you defined for this cluster.

c.     You can optionally specify an alternative proxy configuration to use as the default selection for managed workload clusters.

When you add workload clusters, you can choose which proxy configuration to use. This setting simply indicates the default choice.

8.     Click Next.

When you click NextTanzu Mission Control generates a YAML file that defines how the management cluster connects to Tanzu Mission Control for registration. The credential provided in the YAML expires after 48 hours. You can optionally click View YAML to see the code.

9.     Copy the URL provided on the Register page, and give it to the administrator of your Tanzu Kubernetes Grid deployment to install the cluster agent on your management cluster and complete the registration process.

For clusters running in vSphere or vSphere with Tanzu, this is typically the vSphere administrator.

10.  Click View Management Cluster.


Below  procedure assumes that you have already started the registration process in Tanzu Mission Control.



1.     If you are using a proxy configuration, use the generated tmc command to register the cluster.

a.     In a command window, log in with the Tanzu Mission Control CLI (tmc), making sure you have the latest version.

b.     Run the tmc managementcluster register command provided by Tanzu Mission Control, inserting the appropriate kubeconfig.

For example:

tmc managementcluster register my-mgmt-cluster --kubeconfig my-mgmt-cluster-kubeconfig --continue-bootstrap

2.     Use the generated YAML manifest in a kubectl apply command to register the cluster, if you are not using a proxy configuration.

a.     In a command window, connect to the management cluster with kubectl.

Make sure your current context is set appropriately for the management cluster you want to register, and not one of its workload clusters.

b.     Run a kubectl apply command like the following to start the installation.

Make sure you use the URL provided by Tanzu Mission Control, and that it is enclosed in quotes.

kubectl apply -f ""


When you run the appropriate command, a namespace called vmware-system-tmc is created, and then the Tanzu Mission Control cluster agent is installed on the management cluster. The installation process may take a few minutes.

When the installation is complete, your management cluster is registered with Tanzu Mission Control. You can return to the Tanzu Mission Control console and view the registered cluster on the Management clusters tab of the Administration page. It might take a few minutes for Tanzu Mission Control to start receiving health information from the management cluster.


After you successfully register a management cluster, you can add any existing Tanzu Kubernetes clusters that are currently managed by the management cluster to Tanzu Mission Control

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0 In this post I am going to describe ...