i’ve been having some issues with RKE 1.3 and clusters made of EC2 instances in AWS. With RKE 1.2 I can run

rke up

repeatedly with no issues. Using the same cluster state file and RKE 1.3, I continually get stuck with one of the nodes not able to be found. I can’t find anything online that is an exact match for this problem. Anyone else experience this? I opened this github issue with details https://github.com/rancher/rke/issues/3091

I’ve had a similar experience. Make sure you’re using the latest version (1.3.16 now I think) and set drain node to false and enable_cri_dockerd to true

no difference for my cluster unfortunately. also the enable_cri_dockerd flag is only valid for k8s >= 1.24 i think? definitely not for 1.20