検索

@[email protected] @[email protected] Well, #Rancher now owned by #SUSE, so that tracks! But I've ran #k3s on #CentOSStream and #AlmaLinux successfully as well. I think I've only deployed #RKE2 on SUSE variants (SLE Micro, Elemental OS, OpenSUSE Leap Transactional Server).

I think I've finally tamed this #OpenSearch setup on this #Rancher #RKE2 cluster. Today's adventure was schema conflicts. Pods labeled with "app" while others are labeled with app.kubernetes.io cause a problem for inputs as it looks to OpenSearch like there's a string where an object should be and the flatten hashes on the fluentd output wasn't quite enough to cut it, but the dedot filter brought it in the rest of the way there.

Yesterday, I deployed a #Rancher #RKE2 #Kubernetes cluster with #Cilium and removed kube-proxy in the process. Maybe I'm behind the times, but it's the first time I've done cilium (used to flannel, calico, canal, etc.). Looking forward to a simpler and faster Kubernetes!

After doing a number of disk and filesystem migrations, I think this #Rancher #RKE2 cluster has a good start for it's #Longhorn storage. Still have about another 15TB or so to add in the near future at some point. Not nearly as big as our Ceph stuff, but should be plenty enough for what this particular cluster is doing.

Today's #Rancher adventure was seeing what we could break and bring back to life using Longhorn and etcd snapshots on #RKE2 and #k3s.

Basically what I learned last week is that #Rancher #RKE2 is #k3s on steroids and that is awesome. It also means if you're a hobbyist learning #Kubernetes in a self-hosted #homelab, much of the concepts carry over in a familiar way to the bigger "enterprise" product (which is also FOSS).

#Rancher #k3s and #RKE2 get a whole lot of stuff right about #Kubernetes.

Hello, fresh #Rancher #RKE2 cluster. #Kubernetes

Turns out deploying #Rancher #RKE2 is a lot like deploying #K3S. That's a very good thing! Deploying a fresh cluster from scratch is fast! #Kubernetes