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

Fix tabs: add import statements, specify value, spacing

Browse Source
This commit is contained in:
Billy Tat
2022-07-14 20:14:23 -07:00
parent afbabffdeb
commit c55f4b2931
122 changed files with 1162 additions and 712 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.6/v2.6/en/cluster-provisioning/node-requirements/node-requirements.md
+8 -4
View File
@@ -3,6 +3,9 @@ title: Node Requirements for Rancher Managed Clusters
weight: 1
---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
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 three-node cluster running Rancher.
> If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server three-node cluster and downstream clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.]({{<baseurl>}}/rancher/v2.6/en/installation/requirements/)
@@ -31,7 +34,7 @@ For information on how to install Docker, refer to the official [Docker document
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.
>**Note:** In RHEL 8.4, two extra services are included on the NetworkManager: `nm-cloud-setup.service` and `nm-cloud-setup.timer`. These services add a routing table that interferes with the CNI plugin's configuration. If these services are enabled, you must disable them using the command below, and then reboot the node to restore connectivity:
>
>
> ```
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
reboot
@@ -46,7 +49,7 @@ SUSE Linux may have a firewall that blocks all ports by default. In that situati
When [Launching Kubernetes with Rancher]({{<baseurl>}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) using Flatcar Container Linux nodes, it is required to use the following configuration in the [Cluster Config File]({{<baseurl>}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#cluster-config-file)
<Tabs>
<TabItem label="Canal">
<TabItem value="Canal">
```yaml
rancher_kubernetes_engine_config:
@@ -61,9 +64,9 @@ rancher_kubernetes_engine_config:
extra_args:
flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/
```
</TabItem>
<TabItem label="Calico">
</TabItem>
<TabItem value="Calico">
```yaml
rancher_kubernetes_engine_config:
@@ -78,6 +81,7 @@ rancher_kubernetes_engine_config:
extra_args:
flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/
```
</TabItem>
</Tabs>