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, 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.
Use Cloud Enterprise Network (CEN) to connect clusters. This method is applicable to scenarios where clusters reside in different VPCs in different regions and low latency is required. For more information, see Use an Enterprise Edition transit router to establish and secure network communication.
Use east-west gateways to connect clusters. This method is applicable to scenarios where clusters reside in different VPCs in different regions and low costs are required. For more information, see Use east-west ASM gateways to implement cross-network communication among multiple clusters.