This message was deleted.

Copy code

Jun 28 20:23:33 rke2-bld-01 rke2[2805]: time="2023-06-28T20:23:33Z" level=error msg="Kubelet exited: exit status 1"

the kubelet doesn’t like something about your configuration

I mangled a node taint in the config! Getting much farther now!

NAME          STATUS     ROLES                       AGE    VERSION
rke2-bld-01   NotReady   control-plane,etcd,master   4m8s   v1.27.3+rke2r1

Thank you/team for all the hard work on this. Ive been checking this issue almost daily for about a month now. Super stoked to get rke2 running on my pine64 soquartz blade cluster.

it’s all @flat-furniture-58711

✋

Well thank you for your work on this! I've been looking forward to setting up an rke2 arm cluster for quite a while now! Out of curiosity - Would you expect much of a difference in resource utilization between rke2's control plane and the one deployed by k3s (assuming both are deployed in 3 node HA)?

rke2 tends to take more, in our experience