All Products
Search
Document Center

Alibaba Cloud Service Mesh:Multi-cluster management overview

Last Updated:Jan 08, 2025

This topic describes two scenarios of multi-cluster management and provides references for solutions in these two scenarios.

In-cluster service access

In this scenario, cross-cluster service access is not required. Therefore, network connections are not required between clusters on the data plane. By default, Service Mesh (ASM) considers services that are in the same namespace and have the same name in all clusters on the data plane as the same service. Therefore, cross-cluster service calls may occur. To avoid such calls, we recommend that you enable the feature of keeping traffic in-cluster. For more information, see Enable the feature of keeping traffic in-cluster in multi-cluster scenarios.

Cross-cluster service access

In scenarios where cross-cluster service access is required, such as failover, traffic distribution, multi-environment deployment of traffic lanes, and distributed deployment, if clusters reside in different networks, such as across VPCs, across regions, and in hybrid cloud networks, you need to establish network connections between the clusters. The following methods are provided for you to do so.

Deployment type

Description

Connection method

Cross VPCs for Alibaba Cloud clusters

Alibaba Cloud clusters reside in different VPCs

Use CEN or ASM cross-cluster mesh proxies to configure cross-VPC communication for multiple clusters

Cross VPCs for hybrid-cloud clusters

Include Alibaba Cloud clusters, third-party cloud clusters, and self-managed clusters.

Use leased line or ASM cross-cluster mesh proxies to configure cross-VPC communication for multiple clusters