To manage the microservices in your application with Tanzu Service Mesh, you must onboard the clusters where the microservices are deployed. Onboarding involves registering the cluster with Tanzu Service Mesh and installing the necessary components on the cluster.
If you want to first use Tanzu Service Mesh in your testing environment, you can onboard a clean cluster without microservices and namespaces and then deploy a sample application on the cluster. Connect Services Across Clusters with a Global Namespace includes steps on how to deploy the services of a sample application on two clusters.
Verify that your environment meets the requirements listed in Tanzu Service Mesh Environment Requirements and Supported Platforms.
- In the upper-left corner of the Tanzu Service Mesh Console, click Add New and then Onboard New Cluster to open the Onboard Clusters dialog box.
If you're onboarding your first cluster to Tanzu Service Mesh, the Onboard Clusters dialog box appears automatically when you finish signing up for Tanzu Service Mesh
- In the Onboard Clusters dialog box, enter the name that you want your cluster to have in the Tanzu Service Mesh Console.
The cluster name that you enter here can be different from the name of the cluster in your environment. The cluster name cannot contain special characters, such as a number sign (#), at sign (@), apostrophe ('), underscore (_), and uppercase letters.
- Click Generate Security Token to generate a security token.
This security token is used to establish a secure connection between Tanzu Service Mesh and your cluster during the onboarding.
If the Generate Security Token button is unavailable, refresh the browser.
In the box under Then add the token to connect securely with Tanzu Service Mesh, the kubectl command for creating a Kubernetes secret for the security token becomes available.
Under 2 Apply the registration YAML to the cluster, the kubectl command for applying the registration YAML file to the cluster also becomes available. This file contains the Kubernetes configuration required for the registration of the cluster with Tanzu Service Mesh.
- Under 2 Apply the registration YAML to the cluster, click to copy the command for applying the registration YAML.
Do not close the Onboard Clusters dialog box.
- Open a terminal window and set the current context to your cluster:
$ kubectl config use-context cluster_name
- To apply the configuration to your cluster, run the copied YAML registration command.
- Go back to the Onboard Clusters dialog box and under Then add the token to connect securely with Tanzu Service Mesh, click to copy the command for creating a secret for the security token.
- In a terminal window, run the copied command to establish a secure connection to Tanzu Service Mesh using the security token.
The progress bar "Registering cluster with Tanzu Service Mesh" appears in the Onboard Clusters dialog box. Registering the cluster with Tanzu Service Mesh takes a few minutes. When the registration is complete, the Install Service Mesh button becomes available.
- Click Install Service Mesh to install Tanzu Service Mesh on the cluster.
An installation progress bar appears. When the installation is complete, Successfully Onboarded appears next to the cluster name.
- Perform the appropriate step.
To onboard another cluster, click Onboard Another Cluster and repeat steps 1–8.
To close the Onboard Clusters dialog box and display the Tanzu Service Mesh Console, click Exit To Console.
Tanzu Service Mesh displays information about the infrastructure of each onboarded cluster and the microservices deployed there. Tanzu Service Mesh also starts monitoring and collecting infrastructure and service metrics from the cluster (such as number of nodes and services, requests per second, latency, and CPU usage). The Home page of the Tanzu Service Mesh Console provides summary information about the cluster's infrastructure, a visualization of the topology of the services in the cluster, and key metrics. For more information, see View the Summary Infrastructure and Service Information.
What to do next
If you have a multicluster or hybrid-cloud application, you can connect, secure, and manage the services in the application across the clusters with a global namespace. For more information, see Connect Services with a Global Namespace.