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

nit fixes

Browse Source
This commit is contained in:
moelsayed
2018-10-06 01:14:34 +02:00
committed by Denise
parent 05fd96cbd7
commit 2fc98c5844
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/_index.md
+6 -6
View File
@@ -1,5 +1,5 @@
---
title: Removing Rancher from Your Rancher Server Nodes
title: Removing Rancher from Your Rancher Server Nodes
weight: 2000
---
@@ -26,7 +26,7 @@ After you download the tools, complete the following actions:
```
chmod +x system-tools
```
1. Find the kubeconfig file that was generated during your Rancher installation, `kube_config_rancher-cluster.yml`. Move it to the `/.kube` on your workstation, if it isn't already there. Create this directory if it doesn't exist.
1. Find the kubeconfig file that was generated during your Rancher installation, `kube_config_rancher-cluster.yml`. Move it to the `~/.kube` on your workstation, if it isn't already there. Create this directory if it doesn't exist.
System-tools uses this file to access your installation cluster.
@@ -58,9 +58,9 @@ When you run this command, the components listed in [What Gets Removed?](#what-g
| `--force` | Skips the the interactive removal confirmation and removes the Rancher deployment without prompt. |
> <sup>1</sup> If you are working with multiple Kubernetes clusters, you can place `kube_config_rancher-cluster.yml` in another directory path and then set the `KUBECONFIG` environment variable to its path.
>```
export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
```
>```
>export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
>```
## What Gets Removed?
@@ -78,4 +78,4 @@ When removing Rancher from server nodes launched using RKE, the following compon
>**Using 2.0.8 or Earlier?**
>
>These versions of Rancher do not automatically delete the `serviceAccount`, `clusterRole`, and `clusterRoleBindings` resources after the job runs. You'll have to delete them yourself.
>These versions of Rancher do not automatically delete the `serviceAccount`, `clusterRole`, and `clusterRoleBindings` resources after the job runs. You'll have to delete them yourself.