Bring a pre-existing AKS cluster running in a connected Azure account under the management of Tanzu Mission Control.

Prerequisites

Log in to the Tanzu Mission Control console, as described in Log In to the Tanzu Mission Control Console.

Make sure that you are logged in to your Azure account.

Make sure you have the appropriate permissions to manage clusters.
  • To bring an AKS cluster under Tanzu Mission Control management, you must be associated with the managementcluster.admin role, as well as the clustergroup.edit role to add it to a cluster group.
  • You must also have the cluster.admin role on the cluster.
For more information about roles, see Access Control.

Procedure

  1. In the left navigation pane of the Tanzu Mission Control console, click Clusters.
  2. On the Clusters page, click Add cluster, and then choose Manage existing AKS cluster from the dropdown.
  3. Select the account credential you want to use.
  4. Enter the resource ID for the cluster you want to add.
    1. Select the method you want to use to find the resource ID for an existing clusters, either Azure CLI or the Azure portal.
    2. Follow the provided instructions to retrieve the resource ID.
  5. Click Next.
  6. Specify the cluster group name.
    Note: The agent name is a concatenation of the cluster name, region, credential name, and credential type. Use the agent name to refer to the cluster when using the API or CLI.
  7. You can optionally add a label.
  8. You can optionally configure a proxy.
  9. Click Manage.
    Note:

    Following is a list of reasons that prevent a cluster from being managed by Tanzu Mission Control:

    • Kubernetes version is not supported by Tanzu Mission Control
    • Kubernetes versions of any node pool under the cluster are not aligned with the version of the control plane
    • Windows cluster
    • Dual stack cluster
    • Arm architecture cluster
    • Cluster with "AvailabilitySet"
    • A cluster without run command capability (disabled)
    • Cluster already managed by another credential
    • Cluster and Nodepool not in Healthy/Ready state

Results

The cluster is now under Tanzu Mission Control mangement.