Homelab


RWx

There is a saying "make your hobby your job".

I see a lot of advice aimed at people that want to shift into DevOps/Kubernetes to build a homelab. While that's great, and I 100% endorse that, that's not how I started. I have been working in a Kubernetes cluster in production for the past 2 years, and I'm enjoying it that much that I actually want to go the opposite direction, which is to make my job my hobby.

That is kind of the why behind this project, but it's more than that. Besides working on a fun project, I want to take the experience and lessons learned from my job to my own homelab and make it even better. The true value of having a homelab here becomes apparent. Because here I can, not just experiment, but actually implement and deploy all the things that I wouldn't dare do in a production cluster. And if something fails or breaks, I can decide to fix it whenever I want without needing to spend my Friday evening and a good part of the weekend debugging and fixing things, while being chased by management every 4 hours for an update, because a lot of people rely on the cluster (true story, btw).

So with that, I want to continue where I left off. In fact, I want to reset my homelab and start fresh. Now instead of hacking away from the get go, setting up the nodes, installing Talos Linux etc. Let me take a more senior approach and start planning, writing, drawing things out first, before anything else. And this time, I'm planning to document the entire journey/process on this blog and on my new/old GitHub.