This topic provides answers to some frequently asked questions about Fleet management.
Does Fleet management support multiple Fleet instances?
Yes, Fleet management supports multiple Fleet instances. The default Fleet instance quota provided by Distributed Cloud Container Platform for Kubernetes (ACK One) is 1. If you want to create more Fleet instances, log on to the Quota Center console and request a quota increase.
What are the connectivity requirements on clusters that are associated with a Fleet instance?
Make sure that the virtual private cloud (VPC) of the Fleet instance can access the API server of the associated cluster.
Make sure that the VPC of the associated cluster can access the API server of the Fleet instance.
If the Fleet instance and associated cluster belong to different VPCs, you need to use Cloud Enterprise Network (CEN) to connect the VPCs to ensure that the API server of the Fleet instance can communicate with the API server of the associated cluster. You can also enable the public endpoints of the Fleet instance and associated cluster to allow them to communicate over the Internet.
Can I use kubectl to manage Fleet instances?
Yes, you can use kubectl to distribute resources from a Fleet instance. Fleet instances are completely compatible with the Kubernetes API server. You can distribute Kubernetes-native resources from a Fleet instance. You can also use Helm to package an application and then use the Helm CLI to deploy the application to the Fleet 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 Fleet instance and the following error message is displayed: secrets"sec-c58faedb8a7864d3****-public"not find?
Issue
When you associate a cluster with a Fleet instance, the console displays the following error message: secrets"sec-c58faedb8a7864d3****-public"not find.
Cause
The Fleet instance and the cluster to be associated are disconnected. You need to check the connectivity between the Fleet instance and cluster.
Solution
If the Fleet instance and associated cluster belong to different VPCs, you need to use CEN to connect the VPCs to ensure that the API server of the Fleet instance can communicate with the API server of the associated cluster. You can also enable the public endpoints of the Fleet instance and associated cluster to allow them to communicate over the Internet. For more information about CEN, see Cloud Enterprise Network.