mirror of
https://github.com/kubesphere/website.git
synced 2025-12-28 23:02:50 +00:00
Revert capitalization format
Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
This commit is contained in:
Sherlock113
parent
8b78b0dafc
commit
eaf03f7ede
|
|
@ -81,7 +81,7 @@ Docker needs to be installed in advance for this method.
|
|||
privateRegistry: "" # Configure a private image registry for air-gapped installation (e.g. docker local registry or Harbor)
|
||||
```
|
||||
|
||||
2. Input the registry mirror address above and save the file. For more information about the installation process, see [Multi-Node Installation](../../../installing-on-linux/introduction/multioverview/).
|
||||
2. Input the registry mirror address above and save the file. For more information about the installation process, see [Multi-node Installation](../../../installing-on-linux/introduction/multioverview/).
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ As an open-source project on [GitHub](https://github.com/kubesphere), KubeSphere
|
|||
Users are provided with multiple installation options. Please note not all options are mutually exclusive. For instance, you can deploy KubeSphere with minimal packages on multiple nodes in an air-gapped environment.
|
||||
|
||||
- [All-in-One](../../../quick-start/all-in-one-on-linux/): Install KubeSphere on a single node. It is only for users to quickly get familiar with KubeSphere.
|
||||
- [Multi-Node](../multioverview/): Install KubeSphere on multiple nodes. It is for testing or development.
|
||||
- [Multi-node](../multioverview/): Install KubeSphere on multiple nodes. It is for testing or development.
|
||||
- [Air-gapped Installation on Linux](../air-gapped-installation): All images of KubeSphere have been encapsulated into a package. It is convenient for air-gapped installation on Linux machines.
|
||||
- [High Availability Installation](../ha-configuration/): Install high availability KubeSphere on multiple nodes which is used for the production environment.
|
||||
- Minimal Packages: Only install the minimum required system components of KubeSphere. Here is the minimum resource requirement:
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: "Multi-Node Installation"
|
||||
title: "Multi-node Installation"
|
||||
keywords: 'Multi-node, Installation, KubeSphere'
|
||||
description: 'Explain how to install KubeSphere on multiple nodes'
|
||||
linkTitle: "Multi-Node Installation"
|
||||
linkTitle: "Multi-node Installation"
|
||||
weight: 3120
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ In addition to the deployment on cloud, KubeSphere can also be installed on bare
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- Make sure you already know how to install KubeSphere on a multi-node cluster based on the tutorial [Multi-Node Installation](../../../installing-on-linux/introduction/multioverview/).
|
||||
- Make sure you already know how to install KubeSphere on a multi-node cluster based on the tutorial [Multi-node Installation](../../../installing-on-linux/introduction/multioverview/).
|
||||
- Server and network redundancy in your environment.
|
||||
- For a production environment, it is recommended that you prepare persistent storage and create a StorageClass in advance. For development and testing, you can use the integrated OpenEBS to provision LocalPV as the storage service directly.
|
||||
|
||||
|
|
@ -244,7 +244,7 @@ Make `kk` executable:
|
|||
chmod +x kk
|
||||
```
|
||||
|
||||
## Create a Multi-Node Cluster
|
||||
## Create a Multi-node Cluster
|
||||
|
||||
With KubeKey, you can install Kubernetes and KubeSphere together. You have the option to create a multi-node cluster by customizing parameters in the configuration file.
|
||||
|
||||
|
|
|
|||
|
|
@ -334,7 +334,7 @@ To verify if the cluster is highly available, you can turn off an instance on pu
|
|||
|
||||
## See Also
|
||||
|
||||
[Multi-Node Installation](../../../installing-on-linux/introduction/multioverview/)
|
||||
[Multi-node Installation](../../../installing-on-linux/introduction/multioverview/)
|
||||
|
||||
[Kubernetes Cluster Configurations](../../../installing-on-linux/introduction/vars/)
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 5120
|
|||
|
||||
The multi-cluster feature relates to the network connection among multiple clusters. Therefore, it is important to understand the topological relations of clusters.
|
||||
|
||||
## How the Multi-Cluster Architecture Works
|
||||
## How the Multi-cluster Architecture Works
|
||||
|
||||
Before you use the central control plane of KubeSphere to management multiple clusters, you need to create a Host Cluster, also known as **H** Cluster. The H Cluster, essentially, is a KubeSphere cluster with the multi-cluster feature enabled. It provides you with the control plane for unified management of Member Clusters, also known as **M** Cluster. M Clusters are common KubeSphere clusters without the central control plane. Namely, tenants with necessary permissions (usually cluster administrators) can access the control plane from the H Cluster to manage all M Clusters, such as viewing and editing resources on M Clusters. Conversely, if you access the web console of any M Cluster separately, you cannot see any resources on other clusters.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ When you install KubeSphere on Linux, you need to create a configuration file, w
|
|||
|
||||
- If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/), you do not need to create a `config-sample.yaml` file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable Logging in this mode (e.g. for testing purposes), refer to [the following section](#enable-logging-after-installation) to see how Logging can be installed after installation.
|
||||
|
||||
- If you adopt [Multi-Node Installation](../../installing-on-linux/introduction/multioverview/) and are using symbolic links for docker root directory, make sure all nodes follow the exactly same symbolic links. Logging agents are deployed in DaemonSets onto nodes. Any discrepancy in container log path may cause collection failures on that node.
|
||||
- If you adopt [Multi-node Installation](../../installing-on-linux/introduction/multioverview/) and are using symbolic links for docker root directory, make sure all nodes follow the exactly same symbolic links. Logging agents are deployed in DaemonSets onto nodes. Any discrepancy in container log path may cause collection failures on that node.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -335,7 +335,7 @@ To verify if the cluster is highly available, you can turn off an instance on pu
|
|||
|
||||
## See Also
|
||||
|
||||
[Multi-Node Installation](../../../installing-on-linux/introduction/multioverview/)
|
||||
[Multi-node Installation](../../../installing-on-linux/introduction/multioverview/)
|
||||
|
||||
[Kubernetes Cluster Configurations](../../../installing-on-linux/introduction/vars/)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue