I put Kubernetes in my house because I wanted to learn it properly, and the best way to learn a thing is to live with it. Three little nodes, kubeadm, a bit of MetalLB so I had load balancer IPs that meant something on my LAN. It worked. I learned an enormous amount. I would still, gently, advise most people against doing it.
The problem isn't the learning, which was excellent. The problem is that Kubernetes is a system for managing the failure of things at scale, and at home you have neither scale nor enough things failing to justify it. I spent more evenings debugging the cluster than I ever spent debugging the workloads it was supposedly there to run. An etcd quorum wobble on consumer SSDs, a CNI that didn't survive a reboot in the order I rebooted things, certificates quietly approaching expiry. The control plane became the hobby, and the hobby was meant to be the services.
What I actually wanted, it turned out, was to run about a dozen containers reliably and have them come back after a power cut. That's a job for docker-compose and a restart: always, or systemd if you're feeling principled. The "mostly" in the title is doing real work though: I don't regret the year of learning, and when a cluster turns up at work now, none of it is mysterious. I just no longer pretend my house needs one. The cluster's gone. The compose file it replaced has never once paged me.