mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Translation installing on linux chapter, from en version to zh
Signed-off-by: siu <gongshiwen@gmail.com>
This commit is contained in:
siu
parent
4685a91497
commit
d1cff5b5f3
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
linkTitle: "在 Linux 上安装"
|
||||
title: "在 Linux 上安装 KubeSphere"
|
||||
description: "演示如何在云上和本地 Linux 环境中安装 KubeSphere。"
|
||||
layout: "single"
|
||||
|
|
@ -9,13 +10,14 @@ weight: 2000
|
|||
icon: "/images/docs/docs.svg"
|
||||
---
|
||||
|
||||
本章演示如何使用 KubeKey 在 Linux 上配置生产可用的 Kubernetes 和 KubeSphere 集群。您还可以使用 KubeKey 轻松对集群扩缩容，并根据需要设置各种存储类。
|
||||
|
||||
本章演示如何使用 KubeKey 在不同环境的 Linux 上预配置生产就绪的 Kubernetes 和 KubeSphere 集群。 您还可以使用 KubeKey 轻松扩展和缩小集群，并根据需要设置各种存储类。
|
||||
|
||||
## 介绍
|
||||
|
||||
### [概述](../installing-on-linux/introduction/intro/)
|
||||
|
||||
浏览本章的概述，包括安装准备、安装工具和方法以及存储设置。
|
||||
浏览本章的概述，包括安装准备，安装工具和方法以及存储设置。
|
||||
|
||||
### [多节点安装](../installing-on-linux/introduction/multioverview/)
|
||||
|
||||
|
|
@ -24,6 +26,7 @@ icon: "/images/docs/docs.svg"
|
|||
### [端口要求](../installing-on-linux/introduction/port-firewall/)
|
||||
|
||||
了解 KubeSphere 中不同服务的特定端口要求。
|
||||
|
||||
### [Kubernetes 集群配置](../installing-on-linux/introduction/vars/)
|
||||
|
||||
在集群的配置文件中添加自定义设置。
|
||||
|
|
@ -64,10 +67,12 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
从机器上删除 KubeSphere 和 Kubernetes。
|
||||
|
||||
## FAQ
|
||||
|
||||
## 常见问题
|
||||
|
||||
### [为安装配置加速器](../installing-on-linux/faq/configure-booster/)
|
||||
|
||||
|
||||
配置镜像仓库以加快安装速度。
|
||||
|
||||
## 常用指南
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
linkTitle: "Cluster Operation"
|
||||
linkTitle: "集群运维"
|
||||
weight: 2445
|
||||
|
||||
_build:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Add New Nodes"
|
||||
title: "添加新节点"
|
||||
keywords: 'kubernetes, kubesphere, scale, add-nodes'
|
||||
description: 'How to add new nodes in an existing cluster'
|
||||
|
||||
|
|
@ -7,28 +7,31 @@ description: 'How to add new nodes in an existing cluster'
|
|||
weight: 2340
|
||||
---
|
||||
|
||||
When you use KubeSphere for a certain time, most likely you need to scale out your cluster with workloads increasing. In this scenario, KubeSphere provides script to add new nodes to the cluster. Fundamentally the operation is based on Kubelet's registration mechanism, i.e., the new nodes will automatically join the existing Kubernetes cluster.
|
||||
使用 KubeSphere 一段时间后，很可能需要随着工作负载的增加来扩展集群。 在这种情况下，KubeSphere 提供了将新节点添加到集群的脚本。 基本上，该操作基于 Kubelet 的注册机制，即新节点将自动加入现有的Kubernetes 集群。
|
||||
|
||||
{{< notice tip >}}
|
||||
From v3.0.0, the brand-new installer [KubeKey](https://github.com/kubesphere/kubekey) supports scale master amd worker node from a sing-node (all-in-one) cluster.
|
||||
|
||||
从 v3.0.0 起，全新的安装程序 [KubeKey](https://github.com/kubesphere/kubekey) 支持从一个单节点集群扩展主节点和工作节点。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
### Step 1: Modify the Host Configuration
|
||||
### 步骤1：修改主机配置
|
||||
|
||||
KubeSphere supports hybrid environment, that is, the newly added host OS can be CentOS or Ubuntu. When new machines are ready, add the configurations about the new machine information in the `hosts` and `roleGroups` of the file `config-sample.yaml`.
|
||||
KubeSphere 支持混合环境，即新添加的主机操作系统可以是 CentOS 或 Ubuntu 。 准备好新机器后，在文件`config-sample.yaml`的和`roleGroups`中添加有关新机器信息的配置。
|
||||
|
||||
{{< notice warning >}}
|
||||
Do not allowed to modify the host name of the original nodes (e.g. master1) when adding new nodes.
|
||||
添加新节点时，不允许修改原始节点（例如 master1）的主机名。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
For example, if you started the installation with [all-in-one](../../quick-start/all-in-one-on-linux) and you want to add new nodes for the single-node cluster, you can create a configuration file use KubeKey.
|
||||
例如，如果您使用 [all-in-one](../../quick-start/all-in-one-on-linux) 开始安装，并且想要为单节点集群添加新节点 ，您可以使用KubeKey创建配置文件。
|
||||
|
||||
```
|
||||
# Assume your original Kubernetes cluster is v1.17.9
|
||||
./kk create config --with-kubesphere --with-kubernetes v1.17.9
|
||||
```
|
||||
|
||||
The following section demonstrates how to add two nodes (i.e. `node1` and `node2`) using `root` user as an example, it assumes your host name of the first machine is `master1` (Replace the following host name with yours).
|
||||
以下部分以“ root”用户为例，演示如何添加两个节点（即“ node1”和“ node2”），并假设第一台计算机的主机名是“ master1”（用您的主机名替换以下主机名） 。
|
||||
|
||||
```yaml
|
||||
spec:
|
||||
|
|
@ -47,15 +50,15 @@ spec:
|
|||
···
|
||||
```
|
||||
|
||||
### Step 2: Execute the Add-node Command
|
||||
### 步骤2：执行 Add-node 命令
|
||||
|
||||
Execute the following command to apply the changes:
|
||||
执行以下命令以应用更改：
|
||||
|
||||
```bash
|
||||
./kk add nodes -f config-sample.yaml
|
||||
```
|
||||
|
||||
Finally, you will be able to see the new nodes and their information on the KubeSphere console after a successful return. Select **Nodes → Cluster Nodes** from the left menu, or using `kubectl get node` command can also see the changes.
|
||||
执行成功后，您将能够在 KubeSphere 控制台上查看新节点及其信息。 从左侧菜单中选择**节点管理 → 集群节点**，或者使用`kubectl get node`命令也可以看到更改。
|
||||
|
||||
```
|
||||
kubectl get node
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Remove Nodes"
|
||||
title: "删除节点"
|
||||
keywords: 'kubernetes, kubesphere, scale, add-nodes'
|
||||
description: 'How to add new nodes in an existing cluster'
|
||||
|
||||
|
|
@ -7,21 +7,23 @@ description: 'How to add new nodes in an existing cluster'
|
|||
weight: 2345
|
||||
---
|
||||
|
||||
## Cordon a Node
|
||||
## 停止调度节点
|
||||
|
||||
Marking a node as unschedulable prevents the scheduler from placing new pods onto that Node, but does not affect existing Pods on the Node. This is useful as a preparatory step before a node reboot or other maintenance.
|
||||
将节点标记为不可调度可防止调度程序将新的容器放置到该节点上，但不会影响该节点上的现有容器。 这对于节点重新引导或其他维护之前的准备步骤很有用。
|
||||
|
||||
To mark a Node unschedulable, you can choose **Nodes → Cluster Nodes** from the menu, then find a node you want to remove from the cluster and click the **Cordon** button. It takes the same effect with the command `kubectl cordon $NODENAME`, you can see the [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) for more details.
|
||||
若要将节点标记为不可调度，可以从菜单中选择 **节点管理→群集节点 **，然后找到要从群集中删除的节点，然后单击**停止调度**按钮。 它与命令`kubectl cordon $NODENAME`具有相同的效果，有关更多详细信息，请参见 [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/)。
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
Note: Pods that are part of a DaemonSet tolerate being run on an unschedulable Node. DaemonSets typically provide node-local services that should run on the Node even if it is being drained of workload applications.
|
||||
|
||||
注意：作为 DaemonSet 一部分的 Pod 可以在无法调度的节点上运行。 守护程序集通常提供应在节点上运行的节点本地服务，即使正在耗尽工作负载应用程序也是如此。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
## Delete a Node
|
||||
## 删除节点
|
||||
|
||||
You can delete the node by the following command:
|
||||
您可以通过以下命令删除节点：
|
||||
|
||||
```
|
||||
./kk delete node <nodeName> -f config-sample.yaml
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "FAQ"
|
||||
title: "常见问题"
|
||||
keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
||||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
linkTitle: "Introduction"
|
||||
linkTitle: "简介"
|
||||
weight: 2100
|
||||
|
||||
_build:
|
||||
|
|
|
|||
|
|
@ -1,87 +1,88 @@
|
|||
---
|
||||
title: "Overview"
|
||||
title: "概述"
|
||||
keywords: 'Kubernetes, KubeSphere, Linux, Installation'
|
||||
description: 'Overview of Installing KubeSphere on Linux'
|
||||
|
||||
linkTitle: "Overview"
|
||||
linkTitle: "概述"
|
||||
weight: 2110
|
||||
---
|
||||
|
||||
For the installation on Linux, KubeSphere can be installed both in clouds and in on-premises environments, such as AWS EC2, Azure VM and bare metal. Users can install KubeSphere on Linux hosts as they provision fresh Kubernetes clusters. The installation process is easy and friendly. Meanwhile, KubeSphere offers not only the online installer, or [KubeKey](https://github.com/kubesphere/kubekey), but also an air-gapped installation solution for the environment with no Internet access.
|
||||
对于在 Linux 上的安装，KubeSphere 既可以安装在云中也可以安装在本地环境中，例如 AWS EC2，Azure VM 和裸机。 用户可以在配置新的 Kubernetes 集群时在 Linux 主机上安装 KubeSphere。 安装过程简单而友好。 同时，KubeSphere不仅提供在线安装程序或 [KubeKey](https://github.com/kubesphere/kubekey) ，而且还为无法访问 Internet 的环境提供了离线的安装解决方案。
|
||||
|
||||
As an open-source project on [GitHub](https://github.com/kubesphere), KubeSphere is home to a community with thousands of users. Many of them are running KubeSphere for their production workloads.
|
||||
作为 [GitHub](https://github.com/kubesphere) 上的开源项目， 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.
|
||||
为用户提供了多个安装选项。 请注意，并非所有选项都是互斥的。 例如，您可以在离线环境中的多个节点上以最小化部署 KubeSphere。
|
||||
|
||||
- [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.
|
||||
- [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: 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:
|
||||
- [All-in-One](../../../quick-start/all-in-one-on-linux/): 在单个节点上安装 KubeSphere 。 仅用于用户快速熟悉 KubeSphere。
|
||||
- [Multi-Node](../multioverview/): 在多个节点上安装 KubeSphere 。 用于测试或开发。
|
||||
- [Install KubeSphere on Air-gapped Linux](../air-gapped-installation): 把 KubeSphere 的所有镜像打包，方便再 Linux 上离线安装。
|
||||
- High Availability Installation: 在用于生产环境的多个节点上安装高可用性 KubeSphere。
|
||||
- Minimal Packages: 仅安装 KubeSphere 所需的最少系统组件。 以下是最低资源要求:
|
||||
- 2vCPUs
|
||||
- 4GB RAM
|
||||
- 40GB Storage
|
||||
- Full Packages: Install all available system components of KubeSphere such as DevOps, service mesh, and alerting.
|
||||
- [Full Packages](../complete-installation): 安装 KubeSphere 的所有可用系统组件，例如 DevOps，ServiceMesh 和告警。
|
||||
|
||||
For the installation on Kubernetes, see Overview of Installing on Kubernetes.
|
||||
|
||||
## Before Installation
|
||||
有关在 Kubernetes 上进行安装，请参阅在 Kubernetes 上进行安装概述。
|
||||
|
||||
- As images will be pulled and operating systems will be downloaded from the Internet, your environment must have Internet access. Otherwise, you need to use the air-gapped installer instead.
|
||||
- For all-in-one installation, the only one node is both the master and the worker.
|
||||
- For multi-node installation, you need to specify the node roles in the configuration file before installation.
|
||||
- Your linux host must have OpenSSH Server installed.
|
||||
- Please check [Port Requirements](../port-firewall) before installation.
|
||||
## 安装前
|
||||
|
||||
- 由于镜像和操作系统将从网络上下载，因此您的环境必须可以访问 Internet。 否则，您需要改用离线式安装程序。
|
||||
- 对于 All-in-One 安装，唯一的节点是主节点和工作节点。
|
||||
- 对于多节点安装，需要在安装之前在配置文件中指定节点角色。
|
||||
- 您的 Linux 主机必须已安装 OpenSSH 服务。
|
||||
- 在安装之前，请检查[端口要求](../port-firewall) 。
|
||||
|
||||
## KubeKey
|
||||
|
||||
Developed in Go language, KubeKey represents a brand-new installation tool as a replacement for the ansible-based installer used before. KubeKey provides users with flexible installation choices, as they can install KubeSphere and Kubernetes separately or install them at one time, which is convenient and efficient.
|
||||
KubeKey 是用 Go 语言开发的，代表了一种全新的安装工具，可以替代以前使用的基于ansible的安装程序。 KubeKey 为用户提供了灵活的安装选择，因为他们可以分别安装KubeSphere和Kubernetes或一次安装它们，这既方便又高效。
|
||||
|
||||
Three scenarios to use KubeKey:
|
||||
使用 KubeKey 的三种方案：
|
||||
|
||||
- Install Kubernetes only;
|
||||
- Install Kubernetes and KubeSphere together in one command;
|
||||
- Install Kubernetes first, and deploy KubeSphere on it using [ks-installer](https://github.com/kubesphere/ks-installer).
|
||||
- 仅安装Kubernetes;
|
||||
- 在一个命令中一起安装 Kubernetes 和 KubeSphere;
|
||||
- 首先安装Kubernetes，然后使用 [ks-installer](https://github.com/kubesphere/ks-installer) 在 Kubernetes 上部署 KubeSphere。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
If you have existing Kubernetes clusters, please refer to [Installing on Kubernetes](../../../installing-on-kubernetes/).
|
||||
如果您已有 Kubernetes 集群，请参考[在 Kubernetes 上安装](../../../installing-on-kubernetes/)。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
## Quick Installation for Development and Testing
|
||||
## 快速安装用于开发和测试
|
||||
|
||||
KubeSphere has decoupled some components since v2.1.0. KubeKey only installs necessary components by default as this way features fast installation and minimal resource consumption. If you want to enable enhanced pluggable functionalities, see [Enable Pluggable Components](../../../pluggable-components/) for details.
|
||||
自v2.1.0起，KubeSphere 已取消了某些组件的耦合。 默认情况下，KubeKey 仅安装必要的组件，因为这种方法具有安装速度快和资源消耗最少的特点。 如果要启用增强的可插拔功能，请参阅[可插拔组件概述](../../../pluggable-components/)了解详细信息。
|
||||
|
||||
The quick installation of KubeSphere is only for development or testing since it uses local volume for storage by default. If you want a production installation, see HA Cluster Configuration.
|
||||
快速安装KubeSphere仅用于开发或测试，因为默认情况下它使用本地卷进行存储。 如果要进行生产安装，请参阅“ HA群集配置”。
|
||||
|
||||
- **All-in-one**. It means a single-node hassle-free installation with just one command.
|
||||
- **Multi-node**. It allows you to install KubeSphere on multiple instances using the default storage class (local volume), which means it is not required to install storage server such as Ceph and GlusterFS.
|
||||
- **All-in-one**. 这意味着只需一个命令即可进行单节点无忧安装。
|
||||
- **Multi-node**. 它允许您使用默认存储类（本地卷）在多个实例上安装 KubeSphere，这意味着不需要安装存储服务器（例如 Ceph 和 GlusterFS）。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
For air-gapped installation, please refer to [this tutorial](../air-gapped-installation/).
|
||||
关于离线安装，请参考[在 Linux 上离线安装 KubeSphere](../air-gapped-installation/)。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
## Install HA KubeSphere on Linux
|
||||
## 在 Linux 上安装HA KubeSphere
|
||||
|
||||
KubeKey allows users to install a highly available cluster for production. Users need to configure load balancers and persistent storage services in advance.
|
||||
KubeKey 允许用户安装高度可用的群集进行生产。用户需要预先配置负载均衡器和持久性存储服务。
|
||||
|
||||
- [Persistent Storage Configuration](../storage-configuration): By default, KubeKey uses [Local Volume](https://kubernetes.io/docs/concepts/storage/volumes/#local) based on [openEBS](https://openebs.io/) to provide storage services with dynamic provisioning in Kubernetes clusters. It is convenient for the quick installation of a testing environment. In a production environment, it must have a storage server set up. Please refer to [Persistent Storage Configuration](../storage-configuration) for details.
|
||||
- Load Balancer Configuration for HA installation: Before you get started with multi-node installation in a production environment, you need to configure load balancers. Cloud load balancers, Nginx and `HAproxy + Keepalived` all work for the installation.
|
||||
- [持久卷配置](../storage-configuration)：默认情况下，KubeKey 使用基于 [openEBS](https://openebs.io/) 的[本地卷](https://kubernetes.io/docs/concepts/storage/volumes/#local)在 Kubernetes 集群中为存储服务提供动态配置。这对于快速安装测试环境非常方便。在生产环境中，必须设置存储服务器。有关详细信息，请参阅[Persistent Storage Configuration](../storage-configuration)。
|
||||
- [用于HA安装的负载均衡器配置](../master-ha)：在生产环境中开始进行多节点安装之前，需要配置负载均衡器。云负载均衡器，Nginx 和 `HAproxy + Keepalived` 均可用于安装。
|
||||
|
||||
For more information, see HA Cluster Configuration. You can also see the specific step of HA installations across major cloud providers in Installing on Public Cloud.
|
||||
有关更多信息，请参见HA群集配置。您还可以在“在公共云上安装”中看到跨主要云提供商进行HA安装的特定步骤。
|
||||
|
||||
## Overview of Pluggable Components
|
||||
## 可插拔组件概述
|
||||
|
||||
KubeSphere has decoupled some core feature components since v2.1.0. These components are designed to be pluggable, which means you can enable any of them both before and after the installation. By default, KubeKey does not install these pluggable components. For more information, see [Enable Pluggable Components](../../../pluggable-components/).
|
||||
自v2.1.0起，KubeSphere 已取消了一些核心功能组件的耦合。 这些组件被设计为可插拔的，这意味着您可以在安装之前和之后都启用它们。 默认情况下，KubeKey 不安装这些可插入组件。 有关更多信息，请参见[启用可插拔组件](../../../pluggable-components/)。
|
||||
|
||||
|
||||
|
||||
## Storage Configuration Instruction
|
||||
## 存储配置说明
|
||||
|
||||
The following links explain how to configure different types of persistent storage services. Please refer to [Storage Configuration Instruction](../storage-configuration) for detailed instructions regarding how to configure the storage class in KubeSphere.
|
||||
以下链接说明了如何配置不同类型的持久性存储服务。 有关如何在 KubeSphere 中配置存储类的详细说明，请参考[Storage Configuration Instruction](../ storage-configuration)。
|
||||
|
||||
- [NFS](https://kubernetes.io/docs/concepts/storage/volumes/#nfs)
|
||||
- [GlusterFS](https://www.gluster.org/)
|
||||
|
|
@ -89,24 +90,24 @@ The following links explain how to configure different types of persistent stora
|
|||
- [QingCloud Block Storage](https://docs.qingcloud.com/product/storage/volume/)
|
||||
- [QingStor NeonSAN](https://docs.qingcloud.com/product/storage/volume/super_high_performance_shared_volume/)
|
||||
|
||||
## Cluster Operation and Maintenance
|
||||
## 集群运维
|
||||
|
||||
### Add New Nodes
|
||||
### 添加新节点
|
||||
|
||||
With KubeKey, you can scale the number of nodes to meet higher resource needs after the installation, especially in a production environment. For more information, see [Add New Nodes](../../../installing-on-linux/cluster-operation/add-new-nodes/).
|
||||
使用 KubeKey，您可以扩展节点的数量，以在安装后满足更高的资源需求，尤其是在生产环境中。 有关更多信息，请参阅[添加新节点](../../../installing-on-linux/cluster-operation/add-new-nodes/)。
|
||||
|
||||
### Remove Nodes
|
||||
### 删除节点
|
||||
|
||||
You need to drain a node before you remove. For more information, see Remove Nodes.
|
||||
您需要先清空节点，然后再删除。 有关更多信息，请参阅[删除节点](../../cluster-operation/remove-nodes)。
|
||||
|
||||
### Add New Storage Classes
|
||||
### 添加新的存储类
|
||||
|
||||
KubeKey allows you to set a new storage class after the installation. You can set different storage classes for KubeSphere itself and your workloads.
|
||||
KubeKey 允许您在安装后设置新的存储类。 您可以为 KubeSphere 本身和工作负载设置不同的存储类。
|
||||
|
||||
For more information, see Add New Storage Classes.
|
||||
有关更多信息，请参见添加新的存储类。
|
||||
|
||||
## Uninstalling
|
||||
## 卸载
|
||||
|
||||
Uninstalling KubeSphere means it will be removed from the machines, which is irreversible. Please be cautious with the operation.
|
||||
卸载 KubeSphere 意味着将其从计算机中删除，这是不可逆的。 请谨慎操作。
|
||||
|
||||
For more information, see [Uninstalling](../../../installing-on-linux/uninstalling/uninstalling-kubesphere-and-kubernetes/).
|
||||
有关更多信息，请参见[卸载](../../../installing-on-linux/uninstalling/uninstalling-kubesphere-and-kubernetes/)。
|
||||
|
|
|
|||
|
|
@ -1,43 +1,44 @@
|
|||
---
|
||||
title: "Multi-node Installation"
|
||||
title: "多节点安装"
|
||||
keywords: 'Multi-node, Installation, KubeSphere'
|
||||
description: 'Multi-node Installation Overview'
|
||||
|
||||
linkTitle: "Multi-node Installation"
|
||||
linkTitle: "多节点安装"
|
||||
weight: 2112
|
||||
---
|
||||
|
||||
In a production environment, a single-node cluster cannot satisfy most of the needs as the cluster has limited resources with insufficient compute capabilities. Thus, single-node clusters are not recommended for large-scale data processing. Besides, a cluster of this kind is not available with high availability as it only has one node. On the other hand, a multi-node architecture is the most common and preferred choice in terms of application deployment and distribution.
|
||||
在生产环境中，单节点群集无法满足大多数需求，因为该群集的资源有限且计算能力不足。 因此，不建议将单节点群集用于大规模数据处理。 此外，此类群集只有一个节点，因此不具有高可用性。 另一方面，就应用程序部署和分发而言，多节点体系结构是最常见和首选的选择。
|
||||
|
||||
This section gives you an overview of multi-node installation, including the concept, KubeKey and steps. For information about HA installation, refer to Installing on Public Cloud and Installing in On-premises Environment.
|
||||
本节概述了多节点安装，包括概念，KubeKey 和步骤。 有关 HA 安装的信息，请参阅在公有云上安装和在本地环境中安装。
|
||||
|
||||
## Concept
|
||||
## 概念
|
||||
|
||||
A multi-node cluster is composed of at least one master node and one worker node. You can use any node as the **taskbox** to carry out the installation task. You can add additional nodes based on your needs (e.g. for high availability) both before and after the installation.
|
||||
多节点群集由至少一个主节点和一个工作节点组成。 您可以使用任何节点作为“任务箱”来执行安装任务。 您可以在安装之前和之后根据需要添加其他节点（例如，为了实现高可用性）。
|
||||
|
||||
- **Master**. A master node generally hosts the control plane that controls and manages the whole system.
|
||||
- **Worker**. Worker nodes run the actual applications deployed on them.
|
||||
- **Master**. 主节点通常托管控制面，控制和管理整个系统。
|
||||
- **Worker**. 工作节点运行在其上部署的实际应用程序。
|
||||
|
||||
## Why KubeKey
|
||||
## 为什么选择 KubeKey
|
||||
|
||||
If you are not familiar with Kubernetes components, you may find it difficult to set up a highly-functional multi-node Kubernetes cluster. Starting from the version 3.0.0, KubeSphere uses a brand-new installer called KubeKey to replace the old ansible-based installer. Developed in Go language, KubeKey allows users to quickly deploy a multi-node architecture.
|
||||
如果您不熟悉Kubernetes组件，则可能会发现很难建立功能强大的多节点 Kubernetes 集群。 从版本3.0.0开始， KubeSphere 使用一个名为 KubeKey 的全新安装程序来替换旧的基于 ansible 的安装程序。 用 Go 语言开发的 KubeKey 允许用户快速部署多节点体系结构。
|
||||
|
||||
For users who do not have an existing Kubernetes cluster, they only need to create a configuration file with few commands and add node information (e.g. IP address and node roles) in it after KubeKey is downloaded. With one command, the installation will start and no additional operation is needed.
|
||||
对于不具有现有 Kubernetes 集群的用户，下载 KubeKey 之后，他们只需创建带有很少命令的配置文件并在其中添加节点信息（例如IP地址和节点角色）即可。 使用一个命令，即可安装，并且不需要其他操作。
|
||||
|
||||
### Motivation
|
||||
### 优势
|
||||
|
||||
- The previous ansible-based installer has a bunch of software dependencies such as Python. KubeKey is developed in Go language to get rid of the problem in a variety of environments, making sure the installation is successful.
|
||||
- KubeKey uses Kubeadm to install Kubernetes clusters on nodes in parallel as much as possible in order to reduce installation complexity and improve efficiency. It will greatly save installation time compared to the older installer.
|
||||
- With KubeKey, users can scale clusters from an all-in-one cluster to a multi-node cluster, even an HA cluster.
|
||||
- KubeKey aims to install clusters as an object, i.e., CaaO.
|
||||
-
|
||||
之前基于 ansible 的安装程序具有许多软件依赖性，例如 Python。 KubeKey 是使用 Go 语言开发的，可以消除各种环境中的问题，并确保安装成功。
|
||||
- KubeKey 使用 Kubeadm 在节点上尽可能多地并行安装 Kubernetes 集群，以降低安装复杂性并提高效率。 与较早的安装程序相比，它将大大节省安装时间。
|
||||
- 借助 KubeKey，用户可以将群集从多合一群集扩展到多节点群集，甚至是HA群集。
|
||||
- KubeKey 旨在将群集安装为对象，即 CaaO。
|
||||
|
||||
## Step 1: Prepare Linux Hosts
|
||||
## 步骤1：准备 Linux 主机
|
||||
|
||||
Please see the requirements for hardware and operating system shown below. To get started with multi-node installation, you need to prepare at least three hosts according to the following requirements.
|
||||
请参阅下面显示的对硬件和操作系统的要求。 要开始进行多节点安装，您需要根据以下要求准备至少三台主机。
|
||||
|
||||
### System Requirements
|
||||
### 系统要求
|
||||
|
||||
| Systems | Minimum Requirements (Each node) |
|
||||
| 系统 | 最低要求（每个节点） |
|
||||
| ------------------------------------------------------ | ------------------------------------------- |
|
||||
| **Ubuntu** *16.04, 18.04* | CPU: 2 Cores, Memory: 4 G, Disk Space: 40 G |
|
||||
| **Debian** *Buster, Stretch* | CPU: 2 Cores, Memory: 4 G, Disk Space: 40 G |
|
||||
|
|
@ -47,47 +48,31 @@ Please see the requirements for hardware and operating system shown below. To ge
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
The path `/var/lib/docker` is mainly used to store the container data, and will gradually increase in size during use and operation. In the case of a production environment, it is recommended that `/var/lib/docker` should mount a drive separately.
|
||||
`/var/lib/docker`路径主要用于存储容器数据，并且在使用和操作过程中会逐渐增加大小。 在生产环境中，建议`/var/lib/docker`应该分开安装驱动器。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
### Node Requirements
|
||||
### 节点要求
|
||||
|
||||
- All nodes must be accessible through `SSH`.
|
||||
- Time synchronization for all nodes.
|
||||
- `sudo`/`curl`/`openssl` should be used in all nodes.
|
||||
- `docker` can be installed by yourself or by KubeKey.
|
||||
- 所有节点必须可以通过SSH访问。
|
||||
- 所有节点配置时钟同步。
|
||||
- 所有节点必须可以使用`sudo`/`curl`/`openssl` 。
|
||||
- 所有节点必须安装`ebtables`/`socat`/`ipset`/`conntrack` 。
|
||||
- Docker 可以自己安装或由`KubeKey`安装
|
||||
|
||||
{{< notice note >}}
|
||||
### 网络和 DNS 要求
|
||||
|
||||
`docker` must be installed in advance if you want to deploy KubeSphere in an offline environment.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
### Dependency Requirements
|
||||
|
||||
KubeKey can install Kubernetes and KubeSphere together. The dependency that needs to be installed may be different based on the Kubernetes version to be installed. You can refer to the list below to see if you need to install relevant dependencies on your node in advance.
|
||||
|
||||
| Dependency | Kubernetes Version ≥ 1.18 | Kubernetes Version < 1.18 |
|
||||
| ----------- | ------------------------- | ------------------------- |
|
||||
| `socat` | Required | Optional but recommended |
|
||||
| `conntrack` | Required | Optional but recommended |
|
||||
| `ebtables` | Optional but recommended | Optional but recommended |
|
||||
| `ipset` | Optional but recommended | Optional but recommended |
|
||||
|
||||
### Network and DNS Requirements
|
||||
|
||||
- Make sure the DNS address in `/etc/resolv.conf` is available. Otherwise, it may cause some issues of DNS in clusters.
|
||||
- If your network configuration uses Firewall or Security Group, you must ensure infrastructure components can communicate with each other through specific ports. It's recommended that you turn off the firewall or follow the guide [Network Access](https://github.com/kubesphere/kubekey/blob/master/docs/network-access.md).
|
||||
- 确保`/etc/resolv.conf`中的 DNS 地址可用。 否则，可能会导致群集中出现某些DNS问题。
|
||||
- 如果您的网络配置使用防火墙或安全组，则必须确保基础结构组件可以通过特定端口相互通信。 建议您关闭防火墙或遵循指南[网络访问](https://github.com/kubesphere/kubekey/blob/master/docs/network-access.md)。
|
||||
|
||||
{{< notice tip >}}
|
||||
|
||||
- It's recommended that your OS be clean (without any other software installed). Otherwise, there may be conflicts.
|
||||
- A container image mirror (accelerator) is recommended to be prepared if you have trouble downloading images from dockerhub.io. See [Configure registry mirrors for the Docker daemon](https://docs.docker.com/registry/recipes/mirror/#configure-the-docker-daemon).
|
||||
- 建议您的操作系统是干净的（不安装任何其他软件）。 否则可能会发生冲突。
|
||||
- 如果您在从 dockerhub.io 下载镜像时遇到问题，建议准备一个容器镜像（加速器）。 请参阅[Configure registry mirrors for the Docker daemon](https://docs.docker.com/registry/recipes/mirror/#configure-the-docker-daemon)。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
This example includes three hosts as below with the master node serving as the taskbox.
|
||||
本示例包括以下三个主机，其中主节点用作“任务箱”。
|
||||
|
||||
| Host IP | Host Name | Role |
|
||||
| ----------- | --------- | ------------ |
|
||||
|
|
@ -95,15 +80,15 @@ This example includes three hosts as below with the master node serving as the t
|
|||
| 192.168.0.3 | node1 | worker |
|
||||
| 192.168.0.4 | node2 | worker |
|
||||
|
||||
## Step 2: Download KubeKey
|
||||
## 步骤2：下载 KubeKey
|
||||
|
||||
Follow the step below to download KubeKey.
|
||||
请按照以下步骤下载 KubeKey。
|
||||
|
||||
{{< tabs >}}
|
||||
|
||||
{{< tab "For users with good network connections to GitHub" >}}
|
||||
{{< tab "访问 Github 困难" >}}
|
||||
|
||||
Download KubeKey from [GitHub Release Page](https://github.com/kubesphere/kubekey/releases/tag/v1.0.0) or use the following command directly.
|
||||
使用以下命令下载 KubeKey:
|
||||
|
||||
```bash
|
||||
wget https://github.com/kubesphere/kubekey/releases/download/v1.0.0/kubekey-v1.0.0-linux-amd64.tar.gz -O - | tar -xz
|
||||
|
|
@ -111,9 +96,9 @@ wget https://github.com/kubesphere/kubekey/releases/download/v1.0.0/kubekey-v1.0
|
|||
|
||||
{{</ tab >}}
|
||||
|
||||
{{< tab "For users with poor network connections to GitHub" >}}
|
||||
{{< tab "访问 Github 很轻松" >}}
|
||||
|
||||
Download KubeKey using the following command:
|
||||
从[GitHub Release Page](https://github.com/kubesphere/kubekey/releases/tag/v1.0.0)下载 KubeKey 或直接使用以下命令。
|
||||
|
||||
```bash
|
||||
wget -c https://kubesphere.io/download/kubekey-v1.0.0-linux-amd64.tar.gz -O - | tar -xz
|
||||
|
|
@ -122,19 +107,20 @@ wget -c https://kubesphere.io/download/kubekey-v1.0.0-linux-amd64.tar.gz -O - |
|
|||
|
||||
{{</ tabs >}}
|
||||
|
||||
Make `kk` executable:
|
||||
|
||||
将执行权授予`kk`:
|
||||
|
||||
```bash
|
||||
chmod +x kk
|
||||
```
|
||||
|
||||
## Step 3: Create a Cluster
|
||||
## 步骤3：创建一个集群
|
||||
|
||||
For multi-node installation, you need to create a cluster by specifying a configuration file.
|
||||
对于多节点安装，您需要通过指定配置文件来创建集群。
|
||||
|
||||
### 1. Create an example configuration file
|
||||
### 1. 创建一个示例配置文件
|
||||
|
||||
Command:
|
||||
命令:
|
||||
|
||||
```bash
|
||||
./kk create config [--with-kubernetes version] [--with-kubesphere version] [(-f | --file) path]
|
||||
|
|
@ -142,27 +128,39 @@ Command:
|
|||
|
||||
{{< notice info >}}
|
||||
|
||||
Supported Kubernetes versions: *v1.15.12*, *v1.16.13*, *v1.17.9* (default), *v1.18.6*.
|
||||
支持的 Kubernetes 版本: *v1.15.12*, *v1.16.13*, *v1.17.9* (default), *v1.18.6*.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
Here are some examples for your reference:
|
||||
以下是一些示例供您参考：
|
||||
|
||||
- You can create an example configuration file with default configurations. You can also specify the file with a different filename, or in a different folder.
|
||||
- 您可以使用默认配置创建示例配置文件。 您还可以使用其他文件名或其他文件夹指定文件。
|
||||
|
||||
```bash
|
||||
./kk create config [-f ~/myfolder/abc.yaml]
|
||||
```
|
||||
|
||||
- You can specify a KubeSphere version that you want to install (e.g. `--with-kubesphere v3.0.0`).
|
||||
- 您可以在`config-sample.yaml`中自定义持久性存储插件（例如NFS Client，Ceph RBD和GlusterFS）。
|
||||
|
||||
```bash
|
||||
./kk create config --with-storage localVolume
|
||||
```
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
默认情况下，KubeKey将安装 [OpenEBS](https://openebs.io/) 来为开发和测试环境配置 [LocalPV](https://kubernetes.io/docs/concepts/storage/volumes/#local)， 对新用户来说很方便。 在此多节点安装示例中，使用默认存储类（本地卷）。 对于生产，请使用NFS/Ceph/GlusterFS/CSI或商业产品作为持久性存储解决方案。 您需要在`config-sample.yaml`的`addons`下指定它们。 有关更多详细信息，请参见 [Persistent Storage Configuration](../storage-configuration)。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
- 您可以指定要安装的 KubeSphere 版本（例如`--with-kubesphere v3.0.0`）。
|
||||
|
||||
```bash
|
||||
./kk create config --with-kubesphere [version]
|
||||
```
|
||||
|
||||
### 2. Edit the configuration file
|
||||
### 2. 编辑配置文件
|
||||
|
||||
A default file **config-sample.yaml** will be created if you do not change the name. Edit the file and here is an example of the configuration file of a multi-node cluster with one master node.
|
||||
如果不更改名称，将创建默认文件 **config-sample.yaml**。 编辑文件，这是具有一个主节点的多节点群集的配置文件示例。
|
||||
|
||||
```yaml
|
||||
spec:
|
||||
|
|
@ -186,21 +184,21 @@ spec:
|
|||
|
||||
#### Hosts
|
||||
|
||||
- List all your machines under `hosts` and add their detailed information as above. In this case, port 22 is the default port of SSH. Otherwise, you need to add the port number after the IP address. For example:
|
||||
- 在`hosts`下列出您的所有计算机，并如上所述添加其详细信息。 在这种情况下，端口22是SSH的默认端口。 否则，您需要在IP地址后面添加端口号。 例如：
|
||||
|
||||
```yaml
|
||||
hosts:
|
||||
- {name: master, address: 192.168.0.2, internalAddress: 192.168.0.2, port: 8022, user: ubuntu, password: Testing123}
|
||||
```
|
||||
|
||||
- For default root user:
|
||||
- 默认是root用户:
|
||||
|
||||
```yaml
|
||||
hosts:
|
||||
- {name: master, address: 192.168.0.2, internalAddress: 192.168.0.2, password: Testing123}
|
||||
```
|
||||
|
||||
- For passwordless login with SSH keys:
|
||||
- 使用SSH密钥的无密码登录：
|
||||
|
||||
```yaml
|
||||
hosts:
|
||||
|
|
@ -209,34 +207,24 @@ hosts:
|
|||
|
||||
#### roleGroups
|
||||
|
||||
- `etcd`: etcd node names
|
||||
- `master`: Master node names
|
||||
- `worker`: Worker node names
|
||||
- `etcd`: etcd节点名称
|
||||
- `master`: Master节点名称
|
||||
- `worker`: Worker节点名称
|
||||
|
||||
#### controlPlaneEndpoint (for HA installation only)
|
||||
#### controlPlaneEndpoint (仅用于 HA 安装)
|
||||
|
||||
`controlPlaneEndpoint` allows you to define an external load balancer for an HA cluster. You need to prepare and configure an external load balancer if and only if you need to install more than 3 master nodes. Please note that the address and port should be indented by two spaces in `config-sample.yaml`, and the `address` should be VIP. See HA Configuration for details.
|
||||
`controlPlaneEndpoint` 允许您为HA集群定义外部负载均衡器。 当且仅当您需要安装3个以上的主节点时，才需要准备和配置外部负载均衡器。 请注意，地址和端口应在 `config-sample.yaml`中以两个空格缩进，`address`应为VIP。 有关详细信息，请参见HA配置。
|
||||
|
||||
{{< notice tip >}}
|
||||
|
||||
- You can enable the multi-cluster feature by editing the configuration file. For more information, see Multi-cluster Management.
|
||||
- You can also select the components you want to install. For more information, see [Enable Pluggable Components](../../../pluggable-components/). For an example of a complete config-sample.yaml file, see [this file](https://github.com/kubesphere/kubekey/blob/master/docs/config-example.md).
|
||||
- 您可以通过编辑配置文件来启用多集群功能。 有关更多信息，请参阅多集群管理。
|
||||
- 您也可以选择要安装的组件。 有关更多信息，请参见[启用可插拔组件](../../../pluggable-components/)。 有关完整的config-sample.yaml文件的示例，请参见[此文件](https://github.com/kubesphere/kubekey/blob/master/docs/config-example.md)。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
#### addons
|
||||
完成编辑后，保存文件。
|
||||
|
||||
You can customize persistent storage plugins (e.g. NFS Client, Ceph RBD, and GlusterFS) by specifying storage under the field `addons` in `config-sample.yaml`. For more information, see [Persistent Storage Configuration](../storage-configuration).
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
KubeKey will install [OpenEBS](https://openebs.io/) to provision [LocalPV](https://kubernetes.io/docs/concepts/storage/volumes/#local) for development and testing environment by default, which is convenient for new users. In this example of multi-node installation, the default storage class (local volume) is used. For production, please use NFS/Ceph/GlusterFS/CSI or commercial products as persistent storage solutions.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
When you finish editing, save the file.
|
||||
|
||||
### 3. Create a cluster using the configuration file
|
||||
### 3. 使用配置文件创建集群
|
||||
|
||||
```bash
|
||||
./kk create cluster -f config-sample.yaml
|
||||
|
|
@ -244,15 +232,15 @@ When you finish editing, save the file.
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You need to change `config-sample.yaml` above to your own file if you use a different name.
|
||||
如果使用其他名称，则需要将上面的`config-sample.yaml`更改为您自己的文件。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
The whole installation process may take 10-20 minutes, depending on your machine and network.
|
||||
整个安装过程可能需要10到20分钟，具体取决于您的计算机和网络。
|
||||
|
||||
### 4. Verify the installation
|
||||
### 4. 验证安装
|
||||
|
||||
When the installation finishes, you can see the content as follows:
|
||||
安装完成后，您可以看到如下内容：
|
||||
|
||||
```bash
|
||||
#####################################################
|
||||
|
|
@ -276,21 +264,21 @@ https://kubesphere.io 20xx-xx-xx xx:xx:xx
|
|||
#####################################################
|
||||
```
|
||||
|
||||
Now, you will be able to access the web console of KubeSphere at `http://{IP}:30880` (e.g. you can use the EIP) with the account and password `admin/P@88w0rd`.
|
||||
现在，您可以使用帐户和密码`admin/P@88w0rd`访问位于`http://{IP}:30880`的KubeSphere Web控制台（例如，您可以使用EIP）。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
To access the console, you may need to forward the source port to the intranet port of the intranet IP depending on the platform of your cloud providers. Please also make sure port 30880 is opened in the security group.
|
||||
要访问控制台，您可能需要将源端口转发到 Intranet IP 和端口，具体取决于您的云提供商的平台。 还请确保在安全组中打开了端口30880。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
## Enable kubectl Autocompletion
|
||||
## 启用 kubectl 自动补全
|
||||
|
||||
KubeKey doesn't enable kubectl autocompletion. See the content below and turn it on:
|
||||
KubeKey 不会启用 kubectl 自动补全功能。 请参阅下面的内容并将其打开：
|
||||
|
||||
**Prerequisite**: make sure bash-autocompletion is installed and works.
|
||||
**先决条件**：确保已安装 bash-autocompletion 并可以正常工作。
|
||||
|
||||
```bash
|
||||
# Install bash-completion
|
||||
|
|
@ -303,7 +291,9 @@ echo 'source <(kubectl completion bash)' >>~/.bashrc
|
|||
kubectl completion bash >/etc/bash_completion.d/kubectl
|
||||
```
|
||||
|
||||
Detailed information can be found [here](https://kubernetes.io/docs/tasks/tools/install-kubectl/#enabling-shell-autocompletion).
|
||||
|
||||
## Demo
|
||||
详细信息[见此](https://kubernetes.io/docs/tasks/tools/install-kubectl/#enabling-shell-autocompletion)。
|
||||
|
||||
## 示例
|
||||
<script src="https://asciinema.org/a/364501.js" id="asciicast-364501" async></script>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,13 @@
|
|||
---
|
||||
title: "Port Requirements"
|
||||
title: "端口要求"
|
||||
keywords: 'Kubernetes, KubeSphere, port-requirements, firewall-rules'
|
||||
description: 'Port requirements in KubeSphere'
|
||||
|
||||
linkTitle: "Port Requirements"
|
||||
linkTitle: "端口要求"
|
||||
weight: 2120
|
||||
---
|
||||
|
||||
|
||||
KubeSphere requires certain ports for the communications among services. If your network is configured with firewall rules, you need to ensure infrastructure components can communicate with each other through specific ports that act as communication endpoints for certain processes or services.
|
||||
KubeSphere 需要某些端口用于服务之间的通信。 如果您的网络配置有防火墙规则，则需要确保基础组件可以通过特定端口相互通信。
|
||||
|
||||
|Service|Protocol|Action|Start Port|End Port|Notes
|
||||
|---|---|---|---|---|---|
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
---
|
||||
title: "Kubernetes Cluster Configuration"
|
||||
title: "Kubernetes集群配置"
|
||||
keywords: 'KubeSphere, kubernetes, docker, cluster, jenkins, prometheus'
|
||||
description: 'Configure cluster parameters before installing'
|
||||
|
||||
linkTitle: "Kubernetes Cluster Configuration"
|
||||
linkTitle: "Kubernetes集群配置"
|
||||
weight: 2130
|
||||
---
|
||||
|
||||
This tutorial explains how to customize the Kubernetes cluster configurations in `config-example.yaml` when you start to use [KubeKey](https://github.com/kubesphere/kubekey) to provision a cluster. You can reference the following section to understand each parameter.
|
||||
本教程介绍了当您开始使用 [KubeKey](https://github.com/kubesphere/kubekey) 来配置集群时，如何在`config-example.yaml` 中自定义 Kubernetes 集群配置。 您可以参考以下部分以了解每个参数。
|
||||
|
||||
```yaml
|
||||
######################### Kubernetes #########################
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
linkTitle: "Installing in On-premises Environments"
|
||||
linkTitle: "在本地环境中安装"
|
||||
weight: 2200
|
||||
|
||||
_build:
|
||||
render: false
|
||||
---
|
||||
|
||||
In this chapter, we will demonstrate how to use KubeKey or Kubeadm to provision a new Kubernetes and KubeSphere cluster on some on on-premises environments, such as VMware vSphere, OpenStack, Bare Metal, etc. You just need prepare the machines with supported operating system before you start installation. The air-gapped installation guide is also included in this chapter.
|
||||
在本章中，我们将演示如何使用KubeKey或Kubeadm在某些本地环境（例如VMware vSphere，OpenStack，Bare Metal等）上配置新的Kubernetes和KubeSphere集群。在开始安装前，您只需要准备支持的操作系统的机器即可。 离线安装指南也包括在本章中。
|
||||
|
|
@ -82,7 +82,7 @@ vip 所在的是虚拟 IP，并不需要创建主机，所以只需要创建8台
|
|||
|
||||
### yum 安装
|
||||
|
||||
在主机为lb-0和lb-1中部署keepalived+haproxy 即IP为10.10.71.77与10.10.71.66的服务器上安装部署haproxy、keepalived、psmisc
|
||||
在主机为 lb-0 和 lb-1 中部署 keepalived+haproxy 即IP为10.10.71.77与10.10.71.66的服务器上安装部署haproxy、keepalived、psmisc
|
||||
|
||||
```bash
|
||||
yum install keepalived haproxy psmisc -y
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
linkTitle: "Installing on Public Cloud"
|
||||
linkTitle: "在公共云上安装"
|
||||
weight: 2200
|
||||
|
||||
_build:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Deploy KubeSphere on Azure VM Instance"
|
||||
title: "在Azure VM实例上部署KubeSphere"
|
||||
keywords: "KubeSphere, Installation, HA, high availability, load balancer, Azure"
|
||||
description: "The tutorial is for installing a high-availability cluster on Azure."
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Uninstalling"
|
||||
title: "卸载"
|
||||
keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
||||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Uninstalling KubeSphere and Kubernetes"
|
||||
title: "卸载 KubeSphere 和 Kubernetes"
|
||||
keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
||||
description: 'How to uninstall KubeSphere and kubernetes'
|
||||
|
||||
|
|
@ -7,19 +7,21 @@ description: 'How to uninstall KubeSphere and kubernetes'
|
|||
weight: 2451
|
||||
---
|
||||
|
||||
You can delete the cluster by the following command.
|
||||
您可以通过以下命令删除集群。
|
||||
|
||||
{{< notice tip >}}
|
||||
Uninstall will remove KubeSphere and Kubernetes from the machines. This operation is irreversible and does not have any backup. Please be caution with operation.
|
||||
|
||||
卸载将会从计算机中删除 KubeSphere 和 Kubernetes。 此操作是不可逆的，没有任何备份。 请谨慎操作。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
- If you started with the quick start (all-in-one):
|
||||
- 如果您以快速入门 ( all-in-one )开始：
|
||||
|
||||
```
|
||||
./kk delete cluster
|
||||
```
|
||||
|
||||
- If you started with the advanced mode (created with a configuration file):
|
||||
- 如果从高级模式开始（使用配置文件创建）：
|
||||
|
||||
```
|
||||
./kk delete cluster [-f config-sample.yaml]
|
||||
|
|
|
|||
Loading…
Reference in New Issue