This message was deleted.

If you look on docs.rke2.io you can find a known issues page. There're two things on there that come to mind. First is that firewalld screws with RKE2 so you need to disable it. Second is that there's a config change needed for NetworkManager for Calico & Flannel (default CNI for RKE2 being Canal which is Calico+Flannel combined). 10.42.0.0/16 is, I think, the pod network (either that or 10.43, one's pod, the other is service). As I recall with RKE2 by default if you have >1 node, you'll see that flannel sets up your routing table so that 10.42.#.0/24 goes to a given node if you type

route -n

from one of the nodes. So those are the generic things I can think to check. Good luck.

Thank you for your help and kind words. I have already checked RKE2 docs and known issues. I am performing following task before RKE2 install:

tee /etc/NetworkManager/conf.d/cni.conf <<EOF
[keyfile]
unmanaged-devices=interface-name:cni0;interface-name:flannel.1;interface-name:cali*
EOF

sudo systemctl restart NetworkManager

I also don't have firewalld installed. My NetworkManager is of version 1.40.16-15.el8, which don't require node restart, just systemctl restart. Here are my steps, in short: • NetworkManager conf • Disable Swap • Dnf update, time sync, locale set up • Dnf nfs-utils cryptsetup iscsi-initiator-utils Install RKE2

curl -sfL <https://get.rke2.io> | INSTALL_RKE2_VERSION=v1.27.11+rke2r1 sh -
systemctl enable --now rke2-server.service

• Helm Install • Rancher stable repo add • Jetstack repo add • Certmanager install Install Rancher

kubectl create namespace cattle-system
helm install rancher rancher-stable/rancher \
--namespace cattle-system \
--set hostname=<http://droplet1.inharmonyapp.com|droplet1.inharmonyapp.com> \
--set bootstrapPassword=admin \
--set replicas=3

Unless you explicitly uninstalled firewalld, it tends to be installed and enabled by default on RHEL-variants. It was on CentOS7 and Rocky & RHEL 8 last I checked. I know CentOS Stream did weird things, but you might still need to check it. Past that I'd verify with cert manager before installing Rancher because if your pods have trouble talking to each other they should have trouble from the start.