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

Add Prefix Path documentation

Browse Source
This commit is contained in:
galal-hussein
2019-07-15 15:32:37 -07:00
committed by Denise Schannon
parent 25965f66b8
commit 96616b7f23
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/config-options/_index.md
+6 -6
View File
@@ -92,17 +92,17 @@ If you want to use a different version from the supported list, please use the [
### Prefix Path ### Prefix Path
As a part of cluster provisioning, RKE uploads config files' content - `/etc/kubernetes`,`/var/lib/etcd`, etc - to the worker nodes. By default, these configs get stored under `/`. For some operating systems including ROS, and CoreOS, RKE stores its resources to a different prefix path, this prefix path is by default for these operating systems is:
For some operating systems like RancherOS and CoreOS, the location is `/opt/rke` instead of `/`. With that, `/etc/kubernetes` will be stored in `/opt/rke/etc/kubernetes`, `/var/lib/etcd` will be stored in `/opt/rke/var/lib/etcd`, and so on. ```
/opt/rke
To change the default prefix path for any type of cluster, you can use the following option in the cluster configuration file `cluster.yml`: ```
So `/etc/kubernetes` will be stored in `/opt/rke/etc/kubernetes` and `/var/lib/etcd` will be stored in `/opt/rke/var/lib/etcd` etc.
To change the default prefix path for any cluster, you can use the following option in the cluster configuration file `cluster.yml`:
``` ```
prefix_path: /opt/custom_path prefix_path: /opt/custom_path
``` ```
#### **Important: currently there is a limitation when `prefix_path` can not be changed or reset after the cluster is provisioned**
### Cluster Level SSH Key Path ### Cluster Level SSH Key Path
RKE connects to host(s) using `ssh`. Typically, each node will have an independent path for each ssh key, i.e. `ssh_key_path`, in the `nodes` section, but if you have a SSH key that is able to access **all** hosts in your cluster configuration file, you can set the path to that ssh key at the top level. Otherwise, you would set the ssh key path in the [nodes]({{< baseurl >}}/rke/latest/en/config-options/nodes/). RKE connects to host(s) using `ssh`. Typically, each node will have an independent path for each ssh key, i.e. `ssh_key_path`, in the `nodes` section, but if you have a SSH key that is able to access **all** hosts in your cluster configuration file, you can set the path to that ssh key at the top level. Otherwise, you would set the ssh key path in the [nodes]({{< baseurl >}}/rke/latest/en/config-options/nodes/).