This message was deleted.

If you're using selinux, you will likely need to write your own policies to get the correct things allowed. The rke2-selinux policies only cover the default data-dir, not any other one you might decide to use.

Selinux is disabled.

I would probably check out the containerd log then?

I've attached both containerd.log and kubelet.log. To me, it looks like containerd is trying to start some necessary containers, but can't (for some unspecified reason?), and the kubelet is trying to connect to kube-apiserver, but that's not running yet. I don't see any obvious warnings or errors which would tell me what's wrong.

I will admit I have never tried moving the data after the node is up; generally I recommend starting the cluster with the correct paths already set. I kind of wonder if some of the kubeconfig files in the rancher/rke2/agent or rancher/rke2/server/cred directory have the old paths in them - there are some files that we don’t rewrite if they already exist.

Yeah, I believe that will be the root of the problem. I ended up reinstalling each node with the data-dir parameter set before installation and they all work now. Thanks for your help Brad, happy holidays!