Run 8 v2 locals install#

Run 8 v2 locals install#

Rancher also provides scripts to install Docker with one command.ĭocker is not required for RancherD installs. Installing Dockerĭocker is required for Helm chart installs, and it can be installed by following the steps in the official Docker documentation. Currently, RKE2 deploys nginx-ingress as a deployment by default, so you will need to deploy it as a DaemonSet by following these steps. The Ingress should be deployed as DaemonSet to ensure your load balancer can successfully route traffic to all nodes. The RKE2 install is available as of v2.5.6.įor details on which OS versions were tested with RKE2, refer to the support maintenance terms.ĭocker is not required for RKE2 installs. To install RancherD on SELinux Enforcing CentOS 8 or RHEL 8 nodes, some additional steps are required.ĭocker is not required for RancherD installs. Note: RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.Īt this time, only Linux OSes that leverage systemd are supported. If you are installing Rancher on a K3s cluster with Alpine Linux, follow these steps for additional setup. If you are installing Rancher on a K3s cluster with Raspbian Buster, follow these steps to switch to legacy iptables. To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script. To find out which versions of Kubernetes are supported for your Rancher version, refer to the support maintenance terms.

Rancher needs to be installed on a supported Kubernetes version.

Note that the following sysctl setting must be applied: -nf-call-iptables=1įor the container runtime, K3s should work with any modern version of Docker or containerd. RKE Specific Requirementsįor the container runtime, RKE should work with any modern Docker version. If you plan to run Rancher on ARM64, see Running on ARM64 (Experimental). Some users were successful creating a separate firewalld zone with a policy of ACCEPT for the Pod CIDR. If you don’t feel comfortable doing so you might check suggestions in the respective issue. For Kubernetes 1.19 and 1.20, firewalld must be turned off. Some distributions of Linux may have default firewall rules that block communication with Helm. This prevents errors with certificate validation that can occur when the time is not synchronized between the client and server. The ntp (Network Time Protocol) package should be installed. To find out which versions of Kubernetes are supported for your Rancher version, refer to the support maintenance terms.įor details on which OS and Docker versions were tested with each Rancher version, refer to the support maintenance terms.Īll supported operating systems are 64-bit x86. It is not required for RancherD or RKE2 Kubernetes installs. Rancher should work with any modern Linux distribution.ĭocker is required for nodes that will run RKE Kubernetes clusters. Operating Systems and Container Runtime Requirements

The Rancher UI works best in Firefox or Chrome. RancherD on SELinux Enforcing CentOS 8 or RHEL 8 Nodesįor a list of best practices that we recommend for running the Rancher server in production, refer to the best practices section.Operating Systems and Container Runtime Requirements.Make sure the node(s) for the Rancher server fulfill the following requirements: It is important to note that if you install Rancher on a Kubernetes cluster, requirements are different from the node requirements for downstream user clusters, which will run your apps and services. The Rancher server can be installed on a single node or a high-availability Kubernetes cluster. This page describes the software, hardware, and networking requirements for the nodes where the Rancher server will be installed.