Mastodawn

As Hetzner is deprecating dns configuration via the dns-console, I migrated my domains to the new Cloud API. Last piece of the puzzle was to create new tokens and move from the old cert-manager-webhook-hetzner (by vadimkim) to the official chart maintained by Hetzner.

Migrated my 7 kubernetes clusters (k3s, rke2, OpenShift) without major hiccups, only had to do some cleanup due to old acme challenge entries being leftover after the migration (as cert-manager could not remove them without the new webhook and API token).

Only things left are the machines without k3s using lego.

#homelab #hetzner #certmanager #dns #hellyeah #kubernetes #k3s #rke2

Mika Jan 23

#k3s or #k3d? Is there even a difference - and also, what are they useful for? Is it really only good for a quick 'throw-away' #kubernetes cluster for testing, or something? coming from something like #rke2 (which i know is prolly not a good comparison, but still curious how they could be useful to me)

Mika Dec 1

Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.

I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!

🔗 https://github.com/irfanhakim-as/orked

🔗 https://github.com/irfanhakim-as/orked/pull/41

openSUSE Linux Nov 27

Turn your desk into a #DevOps #dojo. Leap 16 + Leap Micro 6.2 make it easy to spin up #VMs, simulate #Kubernetes clusters, and learn cloud-native tooling hands-on—using real tech like #Longhorn, #RKE2, and more.
Explore, break, rebuild. #Linux #opensource #openSUSE https://news.opensuse.org/2025/11/03/leap-fuels-hands-on-learning/

Leap Fuels Hands-On Learning, Exploration

Lifelong learners and tech enthusiasts don’t view openSUSE Leap as just a stable operating system, but a launchpad for discovery. Malcolm, who shared with th...

openSUSE News

Mika Nov 20

Hmm my services are running fine as far as I can tell, but my #Rancher/#RKE2 #Kubernetes cluster is acting up - possibly #etcd related?

Biggest tell being how the control plane/API server not being the most responsive, and some essential pods failing/restarting including #cert-manager, cloud-controller-manager, csi-smb-controller, kube-apiserver, kube-scheduler, rke2-snapshot-controller, csi-provisioner + -resizer, -snapshotter, yadda yadda.

Not sure what could be causing it just yet.

baskin Oct 24

After upgading a Rancher server cluster (3 nodes) to v2.12.2, I was left with a broken UI, sometimes loading sometimes not. Restarting all the nodes one by one and waiting for each one to sync, fixed the issue. In case someone else is hit by that. #kubernetes #rancher #rke2

rdm Oct 10

At #work today I had an unexpectedly pleasant experience. With #kubernetes of all things.

I'm playing around with a sandpit #RKE2 cluster that I'm using to test how things are going to work when we need to deploy an actual working environment, and the matter of persistent storage came up.

A bit of poking around and I discovered #Longhorn. The requirements were trivial - all the required software was already present, just one service needed to be started. And so I installed it via #helm with just a handful of lines in the config.

And it just works. A fully distributed, clustered, read-write-many capable storage subsystem for Kubernetes, and it took me less than the time it is taking to write this to get it up and running.

I fired up a deployment that required multiple RWM PV's and ... it all just worked. I could even go into a management panel and see how the shards were distributed, and how busy everything was.

For a back-end all it needed was a filesystem on each node of the cluster, and even that could be managed with #LVM so it could be expanded at need.

Compared to the old in-tree VMWare CSI operator, this is a dream come true.

#Linux #SysadminLife

[cr0n0s@🐧📡⌨️ 🛠️ ~ ] #Aug 20, 2025

Nueva Entrada en #H4ckseed: Actualizar Versiones de un cluster RKE2

#SysAdmin #Linux #DevOps #RKE2

https://h4ckseed.wordpress.com/2025/08/20/actualizar-versiones-de-un-cluster-rke2/

Actualizar versiones de un clúster RKE2

Por si desconoces, RKE2 es una distribución de Kubernetes desarrollada por Rancher. Además de mejoras de seguridad, la principal diferencia con su antecesora es que ya no está basada en Docker. A v…

h4ckseed

DerFetzer Aug 2, 2025

Moved the last #PostgreSQL cluster from Crunchy Postgres to #CloudNativePG.💪

This was the final step in the long overdue migration from #RKE to #RKE2.

What at ride but went pretty smoothly to be honest!🥳

#kubernetes #homelab #diy

DerFetzer Jul 11, 2025

Spent 4h debugging my #RKE2 #k8s test-cluster only to find out there was an IP address conflict with the #QEMU gateway on the network🙄🙈
Why is there even a gateway on an isolated network?
And yes, it is 2 AM in the morning!😴