Skip to content

Commit 73adeb4

Browse files
DOC-4130 revised changes based on K3s docs
1 parent 879a0aa commit 73adeb4

File tree

1 file changed

+73
-7
lines changed
  • content/integrate/redis-data-integration/ingest/installation

1 file changed

+73
-7
lines changed

content/integrate/redis-data-integration/ingest/installation/_index.md

Lines changed: 73 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,78 @@ You must run the RDI installer as a privileged user because it installs
3434
[containerd](https://containerd.io/) and registers services. However, you don't
3535
need any special privileges to run RDI processes for normal operation.
3636

37-
### Hardware sizing
37+
The [K3s](https://k3s.io/) Kubernetes distribution used by RDI has a few
38+
requirements for cloud VMs that you must implement before running the
39+
RDI installer, or else installation will fail. The following sections
40+
give full pre-installation instructions for [RHEL](#k3s-rhel) and
41+
[Ubuntu](#k3s-ubuntu).
42+
43+
### RHEL {#k3s-rhel}
44+
45+
K3s recommends that you turn off
46+
[`firewalld`](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/using-and-configuring-firewalld_configuring-and-managing-networking)
47+
before installation using the command:
48+
49+
```bash
50+
systemctl disable firewalld --now
51+
```
52+
53+
However, if you do need to use `firewalld`, you must add the following rules:
54+
55+
```bash
56+
firewall-cmd --permanent --add-port=6443/tcp #apiserver
57+
firewall-cmd --permanent --zone=trusted --add-source=10.42.0.0/16 #pods
58+
firewall-cmd --permanent --zone=trusted --add-source=10.43.0.0/16 #services
59+
firewall-cmd --reload
60+
```
61+
62+
You may also need to open other ports if your setup requires them. See the K3s
63+
[Inbound rules](https://docs.k3s.io/installation/requirements?_highlight=red&_highlight=hat&os=rhel#inbound-rules-for-k3s-nodes)
64+
docs for more information. If you change the default CIDR for pods or services,
65+
you must update the firewall rules accordingly.
66+
67+
If you have `nm-cloud-setup.service` enabled, you must disable it and reboot the
68+
node with the following commands:
69+
70+
```bash
71+
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
72+
reboot
73+
```
74+
75+
See
76+
[Rancher support and maintenance terms](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-8-6/)
77+
for more information about the OS versions that have been tested with Rancher
78+
managed K3s clusters.
79+
80+
### Ubuntu {#k3s-ubuntu}
81+
82+
K3s recommends that you turn off
83+
[Uncomplicated Firewall](https://wiki.ubuntu.com/UncomplicatedFirewall) (`ufw`)
84+
before installation with the command:
85+
86+
```bash
87+
ufw disable
88+
```
89+
90+
However, if you do need to use `ufw`, you must add the following rules:
91+
92+
```bash
93+
ufw allow 6443/tcp #apiserver
94+
ufw allow from 10.42.0.0/16 to any #pods
95+
ufw allow from 10.43.0.0/16 to any #services
96+
```
97+
98+
You may also need to open other ports if your setup requires them. See the K3s
99+
[Inbound rules](https://docs.k3s.io/installation/requirements?_highlight=red&_highlight=hat&os=debian#inbound-rules-for-k3s-nodes)
100+
docs for more information. If you change the default CIDR for pods or services,
101+
you must update the firewall rules accordingly.
102+
103+
See
104+
[Rancher support and maintenance terms](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-8-6/)
105+
for more information about the OS versions that have been tested with Rancher
106+
managed K3s clusters.
107+
108+
## Hardware sizing
38109

39110
RDI is mainly CPU and network bound.
40111
Each of the RDI VMs should have:
@@ -46,12 +117,7 @@ Each of the RDI VMs should have:
46117
- Disk: 25GB of disk (this includes the OS footprint)
47118
- 10GB or more network interface
48119

49-
### Installation steps
50-
51-
{{<note>}}Installing RDI on a cloud VM will fail if `nm-cloud-setup.service` is
52-
running. Use `systemctl disable nm-cloud-setup.service` to disable the service
53-
before running the installer.
54-
{{</note>}}
120+
## Installation steps
55121

56122
Follow the steps below for each of your VMs:
57123

0 commit comments

Comments
 (0)