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

Merge pull request #2952 from catherineluse/rancherd

Browse Source 
Say that RancherD install is experimental
This commit is contained in:
Catherine Luse
2021-01-05 20:48:36 -07:00
committed by GitHub
parent ba911285db 297508d221
commit 10ba9dd2ce
3 changed files with 21 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/_index.md
+14 -2
View File
@@ -15,6 +15,8 @@ In this section,
- **The Rancher server** manages and provisions Kubernetes clusters. You can interact with downstream Kubernetes clusters through the Rancher server's user interface.
- **RKE (Rancher Kubernetes Engine)** is a certified Kubernetes distribution and CLI/library which creates and manages a Kubernetes cluster.
- **K3s (Lightweight Kubernetes)** is also a fully compliant Kubernetes distribution. It is newer than RKE, easier to use, and more lightweight, with a binary size of less than 100 MB. As of Rancher v2.4, Rancher can be installed on a K3s cluster.
- **RKE2** is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector.
- **RancherD** is a new tool for installing Rancher, which is experimental as of Rancher v2.5.4. RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then installs the Rancher server Helm chart on the cluster.
# Changes to Installation in Rancher v2.5
@@ -28,13 +30,23 @@ The `restrictedAdmin` Helm chart option was added. When this option is set to tr
Rancher can be installed on these main architectures:
### High-availability Kubernetes Install
### High-availability Kubernetes Install with the Helm CLI
We recommend using Helm, a Kubernetes package manager, to install Rancher on multiple nodes on a dedicated Kubernetes cluster. For RKE clusters, three nodes are required to achieve a high-availability cluster. For K3s clusters, only two nodes are required.
### High-availability Kubernetes Install with RancherD
_Experimental as of v2.5.4_
RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then installs the Rancher server Helm chart on the cluster.
In both the RancherD install and the Helm CLI install, Rancher is installed as a Helm chart on a Kubernetes cluster.
Configuration and upgrading are also simplified with RancherD. When you upgrade the RancherD binary, both the Kubernetes cluster and the Rancher Helm chart are upgraded.
### Single-node Kubernetes Install
Another option is to install Rancher with Helm on a Kubernetes cluster, but to only use a single node in the cluster. In this case, the Rancher server doesn't have high availability, which is important for running Rancher in production.
Rancher can be installed on a single-node Kubernetes cluster. In this case, the Rancher server doesn't have high availability, which is important for running Rancher in production.
However, this option is useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. In the future, you can add nodes to the cluster to get a high-availability Rancher server.
content/rancher/v2.x/en/installation/install-rancher-on-linux/_index.md
+3 -3
View File
@@ -3,9 +3,9 @@ title: Install Rancher on a Linux OS
weight: 2
---
_Available as of Rancher v2.5_
_Experimental as of Rancher v2.5.4_
As part of Rancher 2.5, we are excited to introduce a new, simpler way to install Rancher called RancherD.
We are excited to introduce a new, simpler way to install Rancher called RancherD.
RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then installs the Rancher server Helm chart on the cluster.
@@ -22,7 +22,7 @@ RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then
When RancherD is launched on a host, it first installs an RKE2 Kubernetes cluster, then deploys Rancher on the cluster as a Kubernetes daemonset.
In both the RancherD install and the Helm CLI install, Rancher is installed as a Helm chart on a Kubernetes cluster. A highly available RancherD installation is equally suitable for production compared to a highly available installation using the Helm CLI.
In both the RancherD install and the Helm CLI install, Rancher is installed as a Helm chart on a Kubernetes cluster.
Configuration and upgrading are also simplified with RancherD. When you upgrade the RancherD binary, both the Kubernetes cluster and the Rancher Helm chart are upgraded.
content/rancher/v2.x/en/installation/requirements/_index.md
+4 -2
View File
@@ -29,15 +29,17 @@ Rancher should work with any modern Linux distribution.
### Requirements for Installing Rancher with RancherD
_RancherD installs are experimental as of v2.5.4_
At this time, only Linux OSes that leverage systemd are supported.
To install RancherD on SELinux Enforcing CentOS 8 or RHEL 8 nodes, some [additional steps](#rancherd-on-selinux-enforcing-centos-8-or-rhel-8-nodes) are required.
Docker is not required for RancherD installs.
### Requirements for Installing Rancher on an RKE Kubernetes Cluster
### Requirements for Installing Rancher on an RKE Kubernetes Cluster with the Helm CLI
For the container runtime, RKE should work with any modern Docker version, while K3s should work with any modern version of Docker or containerd.
RKE should work with any modern Docker version, while K3s should work with any modern version of Docker or containerd.
Rancher and RKE have been tested and are supported on Ubuntu, CentOS, Oracle Linux, RancherOS, and RedHat Enterprise Linux.