You are viewing documentation for KubeSphere version:v3.0.0
KubeSphere v3.0.0 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
Manage a Multi-cluster Environment on KubeSphere
KubeSphere provides an easy-to-use multi-cluster feature to help you build your multi-cluster environment on KubeSphere. This guide illustrates how to manage a multi-cluster environment on KubeSphere.
Prerequisites
-
Make sure your Kubernetes clusters are installed with KubeSphere before you use them as your Host Cluster and Member Clusters.
-
Make sure the cluster role is set correctly on your Host Cluster and Member Clusters respectively, and the
jwtSecretis the same between them. -
It is recommended that your Member Cluster is in a clean environment where no resources have been created on it before it is imported to the Host Cluster.
Manage your KubeSphere Multi-cluster Environment
Once you build a multi-cluster environment on KubeSphere, you can manage it through the central control plane from your Host Cluster. When creating resources, you can select a specific cluster while the Host Cluster should be avoided in case of overload. It is not recommended to log in to the KubeSphere web console of your Member Clusters to create resources on them as some resources (for example, workspaces) won’t be synchronized to your Host Cluster for management.
Resource Management
It is not recommended that you change a Host Cluster to a Member Cluster or the other way round. If a Member Cluster has been imported to a Host Cluster before, you have to use the same cluster name when importing it to a new Host Cluster after unbinding it from the previous Host Cluster.
If you want to import the Member Cluster to a new Host Cluster while retaining existing projects (i.e. namespaces), you can follow the steps as below.
-
Run the following command on the Member Cluster to unbind the projects to be retained from your workspace.
kubectl label ns <namespace> kubesphere.io/workspace- && kubectl patch ns <namespace> -p '{"metadata":{"ownerReferences":[]}}' --type=merge -
Run the following command on the Member Cluster to clear your workspace.
kubectl delete workspacetemplate <workspace name> -
When you create a workspace on the new Host Cluster and assign the Member Cluster to this workspace, run the following command on the Member Cluster to bind the projects retained for the workspace.
kuebctl label ns <namespace> kubesphere.io/workspace=<workspace name>
Account Management
The accounts you create through the central control plane from your Host Cluster will be synchronized to Member Clusters.
You can create workspaces and assign different clusters to them. After that, you can invite different accounts to these workspaces per access requirements for these accounts. Besides, you can also invite different accounts after creating multi-cluster projects with different clusters authorized. In this way, you can let different accounts access different clusters.
KubeSphere Components Management
KubeSphere provides some pluggable components that you can enable based on your needs. In a multi-cluster environment, you can choose to enable these components on your Host Cluster or Member Cluster.
For example, you only need to enable the App Store on your Host Cluster and you can use functions related to the App Store on your Member Clusters directly. For other components, when you enable them on your Host Cluster, you still have to manually enable the same components on your Member Cluster to implement the same features. Besides, you can also enable components only on your Member Cluster to implement corresponding features solely on your Member Cluster.
For more information about how to enable pluggable components, refer to Enable Pluggable Components.
Previous
What’s on this Page