mirror of https://github.com/rancher/rke1-docs.git
60 lines
2.1 KiB
Markdown
60 lines
2.1 KiB
Markdown
---
|
|
title: Adding and Removing Nodes
|
|
description: RKE supports adding/removing nodes for worker and controlplane hosts. Learn about the changes you need to make to the cluster.yml in order to add/remove nodes
|
|
---
|
|
|
|
### Adding/Removing Nodes
|
|
|
|
RKE supports adding/removing [nodes](../config-options/nodes/nodes.md) for worker and controlplane hosts.
|
|
|
|
In order to add additional nodes, you update the original `cluster.yml` file with any additional nodes and specify their role in the Kubernetes cluster.
|
|
|
|
In order to remove nodes, remove the node information from the nodes list in the original `cluster.yml`.
|
|
|
|
After you've made changes to add/remove nodes, run `rke up` with the updated `cluster.yml`.
|
|
|
|
### Adding/Removing Worker Nodes
|
|
|
|
You can add/remove only worker nodes, by running `rke up --update-only`. This will ignore everything else in the `cluster.yml` except for any worker nodes.
|
|
|
|
:::note
|
|
|
|
When using `--update-only`, other actions that do not specifically relate to nodes may be deployed or updated, for example [addons](../config-options/add-ons/add-ons.md).
|
|
|
|
:::
|
|
|
|
### Removing Kubernetes Components from Nodes
|
|
|
|
In order to remove the Kubernetes components from nodes, you use the `rke remove` command.
|
|
|
|
:::danger
|
|
|
|
This command is irreversible and will destroy the Kubernetes cluster, including etcd snapshots on S3. If there is a disaster and your cluster is inaccessible, refer to the process for [restoring your cluster from a snapshot](../etcd-snapshots/etcd-snapshots.md#restoring-a-cluster-from-backup).
|
|
|
|
:::
|
|
|
|
The `rke remove` command does the following to each node in the `cluster.yml`:
|
|
|
|
- Remove the Kubernetes component deployed on it
|
|
- `etcd`
|
|
- `kube-apiserver`
|
|
- `kube-controller-manager`
|
|
- `kubelet`
|
|
- `kube-proxy`
|
|
- `nginx-proxy`
|
|
|
|
The cluster's etcd snapshots are removed, including both local snapshots and snapshots that are stored on S3.
|
|
|
|
:::note
|
|
|
|
Pods are not removed from the nodes. If the node is re-used, the pods will automatically be removed when the new Kubernetes cluster is created.
|
|
|
|
:::
|
|
|
|
- Clean each host from the directories left by the services:
|
|
- /etc/kubernetes/ssl
|
|
- /var/lib/etcd
|
|
- /etc/cni
|
|
- /opt/cni
|
|
- /var/run/calico
|