I ran Kubernetes at home for a few months and I'm here to tell you it was, mostly, a mistake. Not because Kubernetes is bad, it's superb at the problem it exists for, but because I do not have that problem in my house and I spent a lot of evenings pretending I did.
The pitch I sold myself was reasonable enough. I use it at work, I wanted to understand it deeper, and self-hosting on a cluster sounded more robust than a pile of containers on one box. So I stood up a small cluster, three nodes, the lot, and started moving services onto it.
The trouble is that everything in my house wants to talk to storage, and storage is where Kubernetes stops being fun for a one-person operation. Stateful workloads, persistent volumes, a storage layer that survives a node rebooting, ingress that routes sensibly, certificates that renew themselves: each one is a solved problem with a well-documented answer, and each answer is another component to install, configure, monitor and eventually debug at an unsociable hour. I wasn't running services any more, I was running a platform for running services, and the platform was the full-time job.
The breaking point was an evening when the films wouldn't play and the cause turned out to be a persistent volume that hadn't reattached cleanly after a node restart. On my old single-box setup that's a docker compose up -d and a shrug. On the cluster it was twenty minutes of kubectl describe, reading events, and remembering which of three storage abstractions was the one actually misbehaving. The family does not care that I've learned a great deal about volume claim binding. They want the telly to work.
So I tore most of it down and went back to a simpler Docker setup for anything the house relies on. Outages dropped to roughly zero. My evenings came back. The lesson, which I clearly had to learn by hand, is that Kubernetes earns its complexity when you have scale, a team, and the kind of churn it's designed to tame. At home I had none of those. I had three nodes and one tired operator, and the complexity was all cost and very little benefit.
The "mostly" in the title is doing honest work, though. I'd keep one thing: it made me much better at the real thing at work, because breaking it at home with no stakes taught me how the pieces actually fit, the way no tutorial ever did. As a deliberate learning lab, kept well away from anything the family depends on, a home cluster is genuinely worth it. As the thing running your house, it's a beautifully engineered way to turn a reboot into an incident. Know which one you're building, because I didn't, and the films paid for it.