@elb just got my hands on a #RaspberryPi. I’m either going to put #k3s on there, or add it as an arm node to my #rke2 cluster. What do people recommend for running as the base os? I’ve read #nixos isn’t so hot on a pi.

Can the Rancher peeps clarify something for me? Does rke2 use /run/k3s/containerd/containerd.sock in any way? I always see references to it. Sometimes for rancher-desktop (makes sense), but at times in the context of a rke2 conversation. #k8s #kubernetes #Rancher #rke2

The documentation for launching #rke2 #k3s clusters from #Rancher is basically non existent.

Have been playing around with #Rancher #RKE2 on Ubuntu 22.04, no need to install Docker etc. anymore, just run the command and go :).
Also used #Cilium #CNI
So far so good! It's a better experience, next step: Try to get Hubble running.
#Kubernetes

@bpg To be clear, I am using #terraform to build both the #rancher management cluster and the downstream #kubernetes clusters that are on #aws #eks and #rke2 platforms.
These are fully encapsulated in Terraform code.(working on getting them both in self service models).

The reason I ask about hybrid to the masses is to see how everyone else is solving the problem of multiple #k8s on different platforms.

Currently just for expediency deploying it with #Ansible using https://github.com/lablabs/ansible-role-rke2, but from what I read so far and a little bit of playing around earlier, all the things from the previous post are inherent to #RKE2 and not brought about by #Ansible.

I'm evaluating #RKE2 for deploying #Kubernetes, and the first issue I'm seeing is the token tying the whole #cluster together. In default operation it's tied to the CA it sets up for itself, but can also be provided as a string.

But from what I've seen so far, there's absolutely no way ever to change it. Like, at all. To the point where changing it in config and restarting the services makes them not come back up. Makes them not come back up even after switching the token to old value 🤣 #fail