DocsICP FilingConsole
官方文档
首页

Manage MCS in the console

更新时间：
复制 MD 格式
产品详情
我的收藏

Manage MCS in the ACK One console to enable cross-cluster access for Kubernetes services.

Overview

MCS enables cross-cluster access for Kubernetes services, enabling Kubernetes services to communicate across cluster boundaries. The following figure shows an example of how MCS works.

多集群服务

  1. An administrator creates application-related resources, including a namespace, deployment, and service, in both the service provider cluster (ACK Cluster 1) and the service consumer cluster (ACK Cluster 2). They also create MCS resources, including a ServiceExport and a ServiceImport.

  2. The Fleet listens for ServiceExport and ServiceImport resources in the associated clusters and synchronizes the endpoints for the corresponding MCS.

  3. In the service consumer cluster (ACK Cluster 2), a client pod can access Service1 in the service provider cluster (ACK Cluster 1).

Prerequisites

Create an MCS

  1. Log on to the ACK One console. In the navigation pane on the left, choose Fleet > Namespace.

  2. On the Namespace page, click Create Namespace. Enter a name for the namespace and click OK.

  3. In the left navigation pane, choose . On the MCS page, click Create Multi-cluster Service.

  4. In the Create Multi-cluster Service panel, select the Service Provider Cluster and Namespace. From the service list, select one to use as the MCS. Then, select the Service Consumer Cluster and click OK.

    MCS supports only ClusterIP services. After you select a service, the panel displays the cross-cluster access methods at the bottom. These methods include the domain names amcs-service1.provider-ns.svc.clusterset.local and service1.provider-ns.svc.clusterset.local. The latter requires the CoreDNS version in the service consumer cluster to be later than 1.9.3.

    On the MCS page, you can view the details of your MCS.

Delete an MCS

On the MCS page, find your MCS and click Delete in the Actions column.