This topic provides answers to some frequently asked questions about the multi-cluster management feature.

Does the multi-cluster management feature support multiple master instances?

Yes, the multi-cluster management feature supports multiple master instances. The default quota of master instances that you can create in Alibaba Cloud Distributed Cloud Container Platform (ACK One) is one. The number of master instances that are supported by the multi-cluster management feature cannot exceed the quota. To increase the quota, go to the Quota Center.

What are the connectivity requirements if I want to use a master instance to manage a cluster that is associated with the master instance?

  1. The virtual private cloud (VPC) in which the master instance resides can connect to the endpoint of the API server of the cluster.
  2. The VPC in which the cluster resides can connect to the endpoint of the API server of the master instance.
  3. If the master instance and the cluster are deployed in different VPCs, you must use Cloud Enterprise Network (CEN) to connect the VPCs. This way, the API server of the master instance and the API server of the cluster can communicate with each other. You can also enable public endpoints for the API servers to communicate with each other over the Internet.

Can I use kubectl to manage a master instance?

Yes, you can use kubectl to distribute resources from a master instance. Master instances are fully compatible with the Kubernetes API server. You can use master instances to distribute Kubernetes resources. You can also use Helm to package applications and then use the Helm CLI to distribute the applications to a master instance. ACK One provides the AMC command-line tool, which runs as a kubectl plug-in. You can use AMC to manage applications and jobs in multi-cluster management scenarios. For more information, see Use AMC.

What do I do if I failed to associate a cluster with a master instance and the following error message is displayed: secrets"sec-c58faedb8a7864d3****-public"not find?

Symptom

When you associate a cluster with a master instance, the console displays the following error message: secrets"sec-c58faedb8a7864d3****-public"not find.

Cause

Connectivity issues exist between the networks of the master instance and the cluster that you want to associate.

Solution

If the master instance and the cluster are deployed in different VPCs, you must use CEN to connect the VPCs. This way, the API server of the master instance and the API server of the cluster can communicate with each other. You can also enable public endpoints for the API servers to communicate with each other over the Internet. For more information about CEN, see Cloud Enterprise Network.