Last updated：2021-05-11 10:41:36
The following conditions must be met before you create a cluster federation:
The target host cluster is created or imported in the KCE console.
The Kubernetes version of the target host cluster is 1.13 or later.
More than 2 CPU cores and 4 GB memory are reserved in the target host cluster.
The cross-region access is enabled for a member cluster if the memory cluster and the host cluster reside in different regions.
Note: If the status of the host cluster is displayed as Not added, the control plane is in normal status. The host cluster is deployed only as the control plane cluster and does not play the member role. In this case, federated resources are not deployed in the host cluster. To allow the host cluster to play the member role, choose More > Join Federation in the Operation column.
For the clusters that reside in regions different from that of the host cluster, select the clusters and manually enable cross-region access.
Click OK. The clusters that reside in the same region as that of the host cluster and the clusters that meet the cross-region access requirements are added to the federation. You can go back to the Federation Management page to view the federation status of the member clusters.
To remove a member cluster from the federation, find the member cluster and click Exit Federation in the Operation column. When a member cluster exits a federation, the resources related to the federation are deleted from the member cluster. If this cluster belongs to another federation, resources in the same namespace are also deleted. Therefore, we recommend that you do not add a cluster to multiple federations.
You can select the option for forcibly exiting the federation. In this case, a force exit is performed regardless of whether abnormal resources exist.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.