public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add cleaning information

Browse Source 
I turn around for hours before finding (https://github.com/rancher/rancher/issues/12237#issuecomment-376839985) - Hope it will help newby like me not wasting time :)
This commit is contained in:
ROUL
2018-10-07 21:18:19 +02:00
committed by GitHub
parent 2fc98c5844
commit 6e069e6f3f
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/cluster-provisioning/rke-clusters/_index.md
+3 -2
View File
@@ -18,9 +18,10 @@ RKE launched clusters are separated into two categories:
- [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/):
For use cases where you want to provision bare-metal servers, on-premise virtual machines, or bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine.
>**Note:** If you have already deploy Kubernetes on a node, and for any reason you wish to reused this node in an another cluster dont forget to clean it by hand after removed it from the previous cluster `sudo rm -rf /var/lib/etcd /etc/kubernetes/ssl /etc/cni /opt/cni /var/lib/cni /var/run/calico /etc/kubernetes/.tmp/`
<br/>
### Requirements
If you use RKE to set up a cluster, your cluster nodes must meet our [Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements).
If you use RKE to set up a cluster, your cluster nodes must meet our [Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements).