So in recent versions of Kubernetes, when pods are killed from a drain event, they go into a state of Failed with the reason being Terminated. They hang out there for a time, but will eventually get GC’d. This can however mess with some stats and it looks kinda scary if you aren’t prepared to see it. I prefer keeping a clean slate so I run a cron that cleans up these pods using this lovely command:
Link to Part 1 In this continuing series we’re setting up the hardware and installing Ubuntu to the HC2s. Let’s get building! Get everything unboxed, and find yourself oddly pleased with how well the cases snap together to form your nice new tower. You can see here what they look like stacked, and you can see the barrel plugs I need to tie into my power supply. I wired up the plugs to a single set of wires to make managing the easier.
This is going to be a multi part blog series about setting up a Kubernetes cluster at home, on a budget. In this first post we’ll talk about the why of this, and speccing out the hardware. I plan for this to be roughly equivalent to a production k8s deployment, using TLS/SSL, enforcing policies, and connecting it to my NAS via NFS for persistent storage where needed. Why do you want a K8s cluster at home?