Container Service for Kubernetes:FAQ about Fleet management

• Does Fleet management support multiple Fleet instances?

• What are the connectivity requirements on clusters that are associated with a Fleet instance?

• Can I use kubectl to manage Fleet instances?

• 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?

• What do I do if an associated cluster fails to be deleted and the status of the namespace is Terminating?

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?

1. Make sure that the virtual private cloud (VPC) of the Fleet instance can access the API server of the associated cluster.

2. Make sure that the VPC of the associated cluster can access the API server of the Fleet instance.

3. 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.

What do I do if an associated cluster fails to be deleted and the status of the namespace is Terminating?

When you remove an associated cluster, some API Services in the associated cluster may be unavailable. As a result, the Fleet namespaces ack-multiple-clusters and ack-cluster-gateway in the associated cluster remain in the Terminating state and cannot be completely deleted. This prevents the cluster from being associated again. You can use one of the following methods to address this issue:

1. Run the following command to obtain the JSON file of the namespace:

   Replace <YOUR_NAMESPACE> in the command with the actual namespace name.

   kubectl get namespace <YOUR_NAMESPACE> -o json > <YOUR_NAMESPACE>.json

2. Delete the array in the finalizers field below spec in the JSON file.

3. Run the following command to delete the namespace in the Terminating state:

   Replace <YOUR_NAMESPACE> in the command with the actual namespace name.

   kubectl replace --raw "/api/v1/namespaces/<YOUR_NAMESPACE>/finalize" -f ./<YOUR_NAMESPACE>.json

4. Run the kubectl get ns command to check whether the namespace in the Terminating state is deleted.