From e6d7b03db287d70416cf210d3a5c9d85a7df2fd6 Mon Sep 17 00:00:00 2001 From: Rodion Miromind Date: Mon, 28 Jun 2021 10:41:23 +0300 Subject: [PATCH] Update multi-cluster-deployment.md --- content/en/blogs/multi-cluster-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blogs/multi-cluster-deployment.md b/content/en/blogs/multi-cluster-deployment.md index 8dfe1163c..26a5cb439 100644 --- a/content/en/blogs/multi-cluster-deployment.md +++ b/content/en/blogs/multi-cluster-deployment.md @@ -95,7 +95,7 @@ KubeSphere 3.0 supports unified management of user access for the multi-cluster ![kubesphere-architecture](https://ap3.qingstor.com/kubesphere-website/docs/kubesphere-architecture.png) -The overall multi-cluster architecture of [KubeSphere](https://kubesphere.io/) is shown above. The cluster where the control plane is located is called Host cluster. The cluster managed by the Host cluster is called Member cluster, which is essentially a Kubernetes cluster with KubeSphere installed. The Host cluster needs to be able to access the kube-apiserver of Member clusters. Besides, there is no requirement for the network connectivity between Member clusters. The Host cluster is independent of the member clusters managed by it, which do not know the existence of the Host cluster. The advantage of the logic is that when the Host cluster malfunctions, Member clusters will not be affected and deployed workloads can continue to run as well. +The overall multi-cluster architecture of KubeSphere [Container Platform](https://kubesphere.io/) is shown above. The cluster where the control plane is located is called Host cluster. The cluster managed by the Host cluster is called Member cluster, which is essentially a Kubernetes cluster with KubeSphere installed. The Host cluster needs to be able to access the kube-apiserver of Member clusters. Besides, there is no requirement for the network connectivity between Member clusters. The Host cluster is independent of the member clusters managed by it, which do not know the existence of the Host cluster. The advantage of the logic is that when the Host cluster malfunctions, Member clusters will not be affected and deployed workloads can continue to run as well. In addition, the Host cluster also serves as an entry for API requests. It will forward all resource requests for member clusters to them. In this way, not only can requests be aggregated, but also authentication and authorization can be implemented in a unified fashion.