Use Tanzu Mission Control to manage an existing EKS cluster running in a connected AWS account.
When you connect an AWS account for cluster lifecycle management with Tanzu Mission Control, the EKS clusters are visible to Tanzu Mission Control, but they are not added into Tanzu Mission Control management by default. To add an AWS EKS cluster into Tanzu Mission Control management, you must identify the EKS cluster you want to add, and then specify the cluster group with which to associate the cluster.
Make sure your EKS clusters satisfy the minimum requirements for lifecycle management through Tanzu Mission Control, as described in Constraints for Lifecycle Management of EKS Clusters.
Make sure that you have edited the
aws-auth configmap to provide lifecycle role access to the EKS cluster, as described in Update aws-auth Configmap for Access to Existing EKS Clusters.
Make sure that you have defined an account credential to provide access to your AWS account, as described in Create an Account Credential for EKS Cluster Lifecycle Management.
Log in to the Tanzu Mission Control console.
Make sure you have the appropriate permissions to create clusters.
To add an AWS EKS cluster into Tanzu Mission Control management, you must be associated with the Tanzu Mission Control cluster.admin role.
- In the Tanzu Mission Control console, click Clusters in the left navigation pane.
- Click Manage existing cluster.
- In section 1 of the Manage existing EKS clusters dialog, specify the AWS Account credential.
You can click Refresh Account Information to refetch the selected account information and populate the rest of the dialog.
- Select the EKS cluster that you want to manage by providing its ARN. You can retrieve the ARN using either the AWS console or the AWS CLI. Paste the cluster ARN into the Cluster ARN field and click Next.
- In section 2 of the Manage existing EKS clusters dialog, specify the name of the cluster group for the newly managed cluster.
When you click Next, Tanzu Mission Control searches for a cluster with that name. If the cluster name already exists, you are prompted to change the name to a Tanzu Mission Control compatible name. The cluster name must start and end with a letter or number, contain only lowercase letters, numbers, and hyphens, and be a maximum length of 63 characters.
For example, if the EKS cluster name is
ABCD, that is an invalid Tanzu Mission Control name, and you are prompted to change the name to a Tanzu Mission Control compatible name. If you change it to
abcd, for example, the agent name changes to
eks.cred_name.region.abcd, while the EKS cluster API will still use
ABCDas the cluster name.
- In section 3 of the Manage existing EKS clusters dialog you can optionally configure the Proxy configuration.
- Click Manage.
The cluster is now under Tanzu Mission Control management. Note that it can take up to five minutes before you can perform lifecycle management actions on your newly managed EKS cluster.