diff --git a/content/en/docs/installing-on-linux/cluster-operation/_index.md b/content/en/docs/installing-on-linux/cluster-operation/_index.md index f57fde055..87f3298fe 100644 --- a/content/en/docs/installing-on-linux/cluster-operation/_index.md +++ b/content/en/docs/installing-on-linux/cluster-operation/_index.md @@ -1,6 +1,6 @@ --- linkTitle: "Cluster Operation" -weight: 2445 +weight: 2300 _build: render: false diff --git a/content/en/docs/installing-on-linux/cluster-operation/add-new-nodes.md b/content/en/docs/installing-on-linux/cluster-operation/add-new-nodes.md index 0f002c77a..d556c9e05 100644 --- a/content/en/docs/installing-on-linux/cluster-operation/add-new-nodes.md +++ b/content/en/docs/installing-on-linux/cluster-operation/add-new-nodes.md @@ -1,34 +1,33 @@ --- title: "Add New Nodes" -keywords: 'kubernetes, kubesphere, scale, add-nodes' -description: 'How to add new nodes in an existing cluster' - +keywords: 'Kubernetes, KubeSphere, scale-up, add-nodes' +description: 'How to add new nodes to 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. +After you use KubeSphere for a certain period of time, it is likely that you need to scale out your cluster with an increasing number of workloads. In this case, KubeSphere provides script to add new nodes to the cluster. Fundamentally, the operation is based on Kubelet's registration mechanism. In other words, the new nodes will automatically join the existing Kubernetes cluster. {{< 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. +From v3.0.0, you can use the brand-new installer [KubeKey](https://github.com/kubesphere/kubekey) to scale the master and worker node from a sing-node (all-in-one) cluster. {{}} ### Step 1: Modify the Host Configuration -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 supports hybrid environments, which means the newly-added host OS can be CentOS or Ubuntu. When new machines are ready, add the configurations of the new machine under `hosts` and `roleGroups` of the file `config-sample.yaml`. {{< notice warning >}} -Do not allowed to modify the host name of the original nodes (e.g. master1) when adding new nodes. +You are not allowed to modify the host name of existing nodes (e.g. master1) when adding new nodes. {{}} -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. +For example, if you start with [all-in-one installation](../../../quick-start/all-in-one-on-linux/), and you want to add new nodes to the single-node cluster, you can create a configuration file using KubeKey. -``` +```bash # 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). +The following section demonstrates how to add two nodes (i.e. `node1` and `node2`) using `root` user as an example. It is assumed that your host name of the first machine is `master1` (Replace the following host name with yours). ```yaml spec: @@ -47,7 +46,7 @@ spec: ··· ``` -### Step 2: Execute the Add-node Command +### Step 2: Execute the Command to Add Nodes Execute the following command to apply the changes: @@ -55,9 +54,9 @@ Execute the following command to apply the changes: ./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. +Finally, you will be able to see the new nodes and their information in KubeSphere console after a successful return. Select **Cluster Nodes** under **Nodes** from the left menu, or use `kubectl get node` command to see the changes. -``` +```bash kubectl get node NAME STATUS ROLES AGE VERSION master1 Ready master,worker 20d v1.17.9 diff --git a/content/en/docs/installing-on-linux/cluster-operation/remove-nodes.md b/content/en/docs/installing-on-linux/cluster-operation/remove-nodes.md index 6ccfe68af..1713a002f 100644 --- a/content/en/docs/installing-on-linux/cluster-operation/remove-nodes.md +++ b/content/en/docs/installing-on-linux/cluster-operation/remove-nodes.md @@ -1,28 +1,27 @@ --- title: "Remove Nodes" -keywords: 'kubernetes, kubesphere, scale, add-nodes' -description: 'How to add new nodes in an existing cluster' - +keywords: 'Kubernetes, KubeSphere, scale, remove-nodes' +description: 'How to remove nodes from 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. +Marking a node as unschedulable prevents the scheduler from placing new pods onto that node while not affecting 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. +To mark a node unschedulable, you can choose **Cluster Nodes** under **Nodes** from the left menu, find a node you want to remove from the cluster, and click the **Cordon** button. Alternatively, you can run the command `kubectl cordon $NODENAME` directly. See [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) for more details. ![Cordon a Node](https://ap3.qingstor.com/kubesphere-website/docs/20200828232951.png) {{< 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. +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. {{}} ## Delete a Node You can delete the node by the following command: -``` +```bash ./kk delete node -f config-sample.yaml ``` diff --git a/content/en/docs/installing-on-linux/uninstalling/uninstalling-kubesphere-and-Kubernetes.md b/content/en/docs/installing-on-linux/uninstalling/uninstalling-kubesphere-and-Kubernetes.md index b74466aaa..99b7ee2ab 100644 --- a/content/en/docs/installing-on-linux/uninstalling/uninstalling-kubesphere-and-Kubernetes.md +++ b/content/en/docs/installing-on-linux/uninstalling/uninstalling-kubesphere-and-Kubernetes.md @@ -1,8 +1,7 @@ --- title: "Uninstalling KubeSphere and Kubernetes" -keywords: 'kubernetes, kubesphere, uninstalling, remove-cluster' -description: 'How to uninstall KubeSphere and kubernetes' - +keywords: 'Kubernetes, KubeSphere, uninstalling, remove-cluster' +description: 'How to uninstall KubeSphere and Kubernetes' weight: 2451 --- @@ -10,17 +9,18 @@ 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. +Uninstall will remove KubeSphere and Kubernetes from your machine. This operation is irreversible and does not have any backup. Please be cautious with the operation. {{}} -- If you started with the quick start (all-in-one): +- If you started with the quickstart (all-in-one): -``` +```bash ./kk delete cluster ``` - If you started with the advanced mode (created with a configuration file): -``` +```bash ./kk delete cluster [-f config-sample.yaml] ``` +