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

Merge pull request #2898 from catherineluse/staging

Browse Source 
Document requirements for RKE cluster with Flatcar Linux nodes
This commit is contained in:
Catherine Luse
2020-12-09 23:07:16 -07:00
committed by GitHub
parent 976fe98c43 3ff77a0714
commit 57542e192e
2 changed files with 37 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/cluster-provisioning/node-requirements/_index.md
+37 -7
View File
@@ -1,13 +1,11 @@
---
title: Node Requirements for User Clusters
title: Node Requirements for Rancher Managed Clusters
weight: 1
---
This page describes the requirements for the nodes where your apps and services will be installed.
This page describes the requirements for the Rancher managed Kubernetes clusters where your apps and services will be installed. These downstream clusters should be separate from the cluster (or single node) running Rancher.
In this section, "user cluster" refers to a cluster running your apps, which should be separate from the cluster (or single node) running Rancher.
> If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server cluster and user clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
> If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server cluster and downstream clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
Make sure the nodes for the Rancher server fulfill the following requirements:
@@ -28,11 +26,15 @@ If you plan to use ARM64, see [Running on ARM64 (Experimental).]({{<baseurl>}}/r
For information on how to install Docker, refer to the official [Docker documentation.](https://docs.docker.com/)
### Oracle Linux and RHEL Derived Linux Nodes
Some distributions of Linux derived from RHEL, including Oracle Linux, may have default firewall rules that block communication with Helm. We recommend disabling firewalld. For Kubernetes 1.19, firewalld must be turned off.
SUSE Linux may have a firewall that blocks all ports by default. In that situation, follow [these steps](#opening-suse-linux-ports) to open the ports needed for adding a host to a custom cluster.
### SUSE Linux Nodes
### Requirements for Windows Nodes
SUSE Linux may have a firewall that blocks all ports by default. In that situation, follow [these steps]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/ports/#opening-suse-linux-ports) to open the ports needed for adding a host to a custom cluster.
### Windows Nodes
_Windows worker nodes can be used as of Rancher v2.3.0_
@@ -40,6 +42,34 @@ Nodes with Windows Server must run Docker Enterprise Edition.
Windows nodes can be used for worker nodes only. See [Configuring Custom Clusters for Windows]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/windows-clusters/)
### Flatcar Linux Nodes
To deploy an RKE Kubernetes cluster using Flatcar Linux (flatcar-linux-stable-2605.6.0) nodes, we recommend the following configuration in the `rancher-cluster.yml`:
{{% accordion label="click to expand" %}}
```yaml
nodes:
- address:
internal_address:
user: core
role: [etcd, controlplane, worker]
ssh_key_path:
network:
plugin: calico
options:
calico_flex_volume_plugin_dir: /opt/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds
flannel_backend_type: vxlan
services:
kube-controller:
extra_args:
flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/
```
{{% /accordion %}}
# Hardware Requirements
The hardware requirements for nodes with the `worker` role mostly depend on your workloads. The minimum to run the Kubernetes node components is 1 CPU (core) and 1GB of memory.
content/rancher/v2.x/en/installation/requirements/ports/_index.md
-4
View File
@@ -213,10 +213,6 @@ When using the [AWS EC2 node driver]({{<baseurl>}}/rancher/v2.x/en/cluster-provi
| Custom UDP Rule | UDP | 30000-32767 | 0.0.0.0/0 | Inbound |
| All traffic | All | All | 0.0.0.0/0 | Outbound |
### Opening Ports with firewalld
[Opening Ports with firewalld]({{<baseurl>}}/rancher/v2.x/en/installation/options/firewall) describes how to use firewalld to apply the above rules.
### Opening SUSE Linux Ports
SUSE Linux may have a firewall that blocks all ports by default. To open the ports needed for adding the host to a custom cluster,