mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Update remove nodes, and re-org some index
Signed-off-by: Ray Zhou <ray@yunify.com>
This commit is contained in:
parent
6e51a55760
commit
d2604593ca
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Add/Delete Nodes"
|
||||
weight: 2300
|
||||
weight: 4400
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Pods that are part of a DaemonSet tolerate being run on an unschedulable node. D
|
|||
|
||||
## Delete a Node
|
||||
|
||||
You can delete the node by the following command:
|
||||
You can delete the node using [KubeKey](https://github.com/kubesphere/kubekey) by the following command. The `config-sample.yaml` file is the one created when you [set up the cluster](../../introduction/multioverview/).
|
||||
|
||||
```bash
|
||||
./kk delete node <nodeName> -f config-sample.yaml
|
||||
|
|
|
|||
|
|
@ -4,5 +4,5 @@ keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
|||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
||||
weight: 2470
|
||||
weight: 4600
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Installing in On-premises Environments"
|
||||
weight: 2200
|
||||
weight: 4300
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Installing on Public Cloud"
|
||||
weight: 2210
|
||||
weight: 4200
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
|||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
||||
weight: 2450
|
||||
weight: 4500
|
||||
---
|
||||
|
||||
Uninstall will remove KubeSphere and Kubernetes from the machines. This operation is irreversible and does not have any backup. Please be caution with operation. You can see [Uninstalling KubeSphere and Kubernetes](../uninstalling-kubesphere-and-kubernetes) for details.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "添加或删除节点"
|
||||
weight: 2445
|
||||
weight: 4400
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, kubesphere, scale, add-nodes'
|
|||
description: 'How to add new nodes in an existing cluster'
|
||||
|
||||
|
||||
weight: 2340
|
||||
weight: 4410
|
||||
---
|
||||
|
||||
使用 KubeSphere 一段时间后,很可能随着工作负载的增加需要扩展集群。在这种情况下,KubeSphere 提供了一个添加新节点的脚本。原理上,该操作是基于 Kubelet 的注册机制,换句话说,新节点将自动加入现有的 Kubernetes 集群中。
|
||||
|
|
|
|||
|
|
@ -1,30 +1,30 @@
|
|||
---
|
||||
title: "删除节点"
|
||||
keywords: 'kubernetes, kubesphere, scale, add-nodes'
|
||||
description: 'How to add new nodes in an existing cluster'
|
||||
keywords: 'kubernetes, kubesphere, scale, delete-nodes'
|
||||
description: '如何删除 KubeSphere 工作节点'
|
||||
|
||||
|
||||
weight: 2345
|
||||
weight: 4420
|
||||
---
|
||||
|
||||
## 停止调度节点
|
||||
|
||||
将节点标记为不可调度可防止调度程序将新的容器放置到该节点上,但不会影响该节点上的现有容器。 这对于节点重新引导或其他维护之前的准备步骤很有用。
|
||||
将节点标记为不可调度可防止调度程序将新的容器放置到该节点上,但不会影响该节点上的现有容器,这对于重启或维护该节点之前的准备步骤很有用。
|
||||
|
||||
若要将节点标记为不可调度,可以从菜单中选择 **节点管理→群集节点 **,然后找到要从群集中删除的节点,然后单击**停止调度**按钮。 它与命令`kubectl cordon $NODENAME`具有相同的效果,有关更多详细信息,请参见 [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/)。
|
||||
若要将节点标记为不可调度,可以从 KubeSphere 菜单中选择**节点管理→集群节点**,找到要从集群中删除的节点,然后单击**停止调度**按钮。或者用命令行执行`kubectl cordon $NODENAME`也能将此节点标记为不可调度,有关更多详细信息,请参见 [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/)。
|
||||
|
||||

|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
注意:作为 DaemonSet 一部分的 Pod 可以在无法调度的节点上运行。 守护程序集通常提供应在节点上运行的节点本地服务,即使正在耗尽工作负载应用程序也是如此。
|
||||
注意:DaemonSet 的 Pod 可以在无法调度的节点上运行。DaemonSet 通常提供节点上运行的本地服务,即使正在驱逐应用程序也不受影响。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
## 删除节点
|
||||
|
||||
您可以通过以下命令删除节点:
|
||||
可以使用 [KubeKey](https://github.com/kubesphere/kubekey) 以下命令删除节点。`config-sample.yaml` 文件是您在[创建该集群](../../introduction/multioverview/)的时候定义的配置文件。
|
||||
|
||||
```
|
||||
```bash
|
||||
./kk delete node <nodeName> -f config-sample.yaml
|
||||
```
|
||||
|
|
|
|||
|
|
@ -4,5 +4,5 @@ keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
|||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
||||
weight: 2470
|
||||
weight: 4600
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, booster, installation, faq'
|
|||
description: 'How to configure a booster for installation'
|
||||
|
||||
|
||||
weight: 2476
|
||||
weight: 4610
|
||||
---
|
||||
|
||||
If you have trouble downloading images from dockerhub.io, it is highly recommended that you configure a registry mirror (i.e. booster) beforehand to speed up downloads. You can refer to the [official documentation of Docker](https://docs.docker.com/registry/recipes/mirror/#configure-the-docker-daemon) or follow the steps below.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "简介"
|
||||
weight: 2100
|
||||
weight: 4100
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "在本地环境中安装"
|
||||
weight: 2200
|
||||
weight: 4300
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "在公共云上安装"
|
||||
weight: 2210
|
||||
weight: 4200
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster'
|
|||
description: 'How to uninstall KubeSphere'
|
||||
|
||||
|
||||
weight: 2450
|
||||
weight: 4500
|
||||
---
|
||||
|
||||
Uninstall will remove KubeSphere and Kubernetes from the machines. This operation is irreversible and does not have any backup. Please be caution with operation. You can see [Uninstalling KubeSphere and Kubernetes](../uninstalling-kubesphere-and-kubernetes) for details.
|
||||
|
|
|
|||
Loading…
Reference in New Issue