Fleet management FAQ

• Does fleet management support multiple Fleet instances?

• Connectivity requirements

• Manage Fleet instances with the kubectl CLI

• Error when adding an associated cluster

• Resolve the "namespace terminating" issue

• Associate an improperly disassociated cluster

Does fleet management support multiple Fleet instances?

Yes. ACK One provides a default quota of one Fleet instance. To create more, request a quota increase in Quota Center.

Connectivity requirements

1. The Fleet instance's VPC must be able to access the associated cluster's API server endpoint.

2. The associated cluster's VPC must be able to access the Fleet instance's API server endpoint.

3. If the Fleet instance and the associated cluster are in different VPCs, connect the VPCs to enable mutual API server access. Use Cloud Enterprise Network (CEN), or enable public endpoints for both.

Manage Fleet instances with the kubectl CLI

Yes. Fleet instances are fully compatible with the Kubernetes API server. Deploy native Kubernetes resources with kubectl, or package and deploy applications with Helm. For multi-cluster scenarios, ACK One provides the AMC Kubectl Plugin. See AMC command-line help.

Error when adding an associated cluster

Symptom

When adding an associated cluster, the console displays this error: secrets "sec-c58faedb8a7864d3****-public" not found.

Cause

The Fleet instance cannot connect to the target cluster. Check network connectivity between the Fleet instance and the cluster to be added.

Solution

If the Fleet instance and the associated cluster are in different VPCs, connect the VPCs to enable mutual API server access. Use Cloud Enterprise Network (CEN), or enable public endpoints for both.

Resolve the "namespace terminating" issue

Disassociating a cluster can make some API Services unavailable, causing the ack-multiple-clusters and ack-cluster-gateway namespaces to get stuck in Terminating state and blocking re-association. To resolve:

1. Retrieve the namespace JSON file.

   Replace <YOUR_NAMESPACE> with your namespace name.

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

2. Open the JSON file and delete the finalizers array from the spec section.

3. Finalize the namespace deletion.

   Replace <YOUR_NAMESPACE> with your namespace name.

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

4. Run kubectl get ns to verify the namespace is deleted.

Associate an improperly disassociated cluster

A Fleet becomes unusable if it or its API server SLB instance is accidentally deleted. Association may report errors when you add a sub-cluster that was not properly disassociated from the old Fleet to a new Fleet. Follow these steps to ensure successful association.

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

2. On the Associated Clusters page, expand the Fleet list, select the new Fleet, and click Add associated clusters.

3. In the Add associated clusters panel, select the cluster and click OK.

4. On the Associated Clusters page, find the cluster you just associated and click Disassociate.

5. Click Add associated clusters again, select the same cluster, and click OK.