mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Merge pull request #2192 from Felixnoo/sync
Remove Stale Docs in 3.1.x Documentation and Update Relevant Docs
This commit is contained in:
commit
f330733b43
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
linkTitle: "Import On-premises Kubernetes Clusters"
|
||||
weight: 5400
|
||||
|
||||
_build:
|
||||
render: false
|
||||
---
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
title: "Import Kubeadm Kubernetes Cluster"
|
||||
keywords: 'kubernetes, kubesphere, multicluster, kubeadm'
|
||||
description: 'Learn how to import a Kubernetes cluster created with kubeadm.'
|
||||
|
||||
|
||||
weight: 5410
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -14,7 +14,9 @@ Before you use the central control plane of KubeSphere to management multiple cl
|
|||
|
||||

|
||||
|
||||
There can only be one H Cluster while multiple M Clusters can exist at the same time. In a multi-cluster architecture, the network between the H Cluster and M Clusters can be connected directly or through an agent. The network between M Clusters can be set in a completely isolated environment.
|
||||
There can only be one H Cluster while multiple M Clusters can exist at the same time. In a multi-cluster architecture, the network between the H Cluster and M Clusters can be [connected directly](../../enable-multicluster/direct-connection/) or [through an agent](../../enable-multicluster/agent-connection/). The network between M Clusters can be set in a completely isolated environment.
|
||||
|
||||
If you are using on-premises Kubernetes clusters built through kubeadm, install KubeSphere on your Kubernetes clusters by referring to [Air-gapped Installation on Kubernetes](../../../installing-on-kubernetes/on-prem-kubernetes/install-ks-on-linux-airgapped/), and then enable KubeSphere multi-cluster management through direct connection or agent connection.
|
||||
|
||||

|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
linkTitle: "导入本地 Kubernetes 集群"
|
||||
weight: 5400
|
||||
|
||||
_build:
|
||||
render: false
|
||||
---
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
title: "Import Kubeadm Kubernetes Cluster"
|
||||
keywords: 'kubernetes, kubesphere, multicluster, kubeadm'
|
||||
description: '了解如何导入通过 kubeadm 创建的 Kubernetes 集群。'
|
||||
|
||||
|
||||
weight: 5410
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -14,7 +14,9 @@ weight: 5120
|
|||
|
||||

|
||||
|
||||
只能有一个 H 集群存在,而多个 M 集群可以同时存在。在多集群架构中,H 集群和 M 集群之间的网络可以直接连接,或者通过代理连接。M 集群之间的网络可以设置在完全隔离的环境中。
|
||||
只能有一个 H 集群存在,而多个 M 集群可以同时存在。在多集群架构中,H 集群和 M 集群之间的网络可以[直接连接](../../enable-multicluster/direct-connection/),或者通过[代理连接](../../enable-multicluster/agent-connection/)。M 集群之间的网络可以设置在完全隔离的环境中。
|
||||
|
||||
如果您是使用通过 kubeadm 搭建的自建 Kubernetes 集群,请参阅[离线安装](../../../installing-on-kubernetes/on-prem-kubernetes/install-ks-on-linux-airgapped/)在您的 Kubernetes 集群上安装 KubeSphere,然后通过直接连接或者代理连接来启用 KubeSphere 多集群管理功能。
|
||||
|
||||

|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue