Kubernetes

I’ve written about Talos Linux as the immutable Kubernetes OS, and I’ve compared Arch vs NixOS for workstations. One question keeps landing in my inbox after both: what about NixOS for the Kubernetes nodes themselves? It’s a fair question, because on paper these two look like siblings. NixOS and Talos are both declarative. Both can be immutable. Both put your configuration under version control. So why pick one over the other to run a cluster? ...

Here is how most of us run Kubernetes nodes. You install a general-purpose Linux distro, harden it with a CIS benchmark script, add an SSH key, set up a config management tool to keep drift in check, and then spend the next two years SSH-ing in to fix the things the config management tool didn’t catch. Every node is a little snowflake with its own history. We’ve accepted this as normal. ...

“We want to migrate to Kubernetes by November.” It was September. The client was an e-commerce company, and their biggest sales event of the year was Black Friday, in late November. I said no. They asked if I knew someone who might take it on anyway. I did. A fellow platform engineer, someone I respect and rate highly. I made the introduction but warned him about the timeline. He took the engagement, documented the same concerns I had, got them signed off. The client proceeded anyway. ...

Every vendor pitch deck right now has the same slide. “Autonomous cluster management.” An AI watches your Kubernetes cluster, spots problems, diagnoses them, and fixes them while you sleep. Platform engineers get to stop firefighting and the cluster heals itself. I run a homelab specifically because I want to understand what’s actually happening, not trust a black box. So when I see a claim like that, my first instinct is to test it myself rather than believe the slide. ...

Here is how most people store their digital lives in 2026. Photos go to Google. Email goes to Gmail. Documents go to whatever cloud came bundled with the phone. Passwords sit in a browser owned by an ad company. Every byte lives on someone else’s server, governed by terms nobody read, in a jurisdiction nobody checked. We hand it all over and we call it normal, because the alternative looks like a second job. ...