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:
Becoming a father Been awhile since I made a blog post. Seems like a lot of my posts start that way… Just over 6 months ago I became a dad. My wife gave birth to our daughter Llyana. She’s a beautiful, wonderful, amazing little girl. For a long time I went back and forth on if I ever wanted to be a dad or not. When my wife and I married, she was pretty against, having kids, and me being wishy-washy on it anyway was fine with that, but as time went on we leaned more and more on wanting a kid.
Upgrading the Franken-CR10S to use the new Hemera In this post I’m going to talk a bit about my migration away from the dual E3D Volcano setup I’ve been using on my Frankensteined CR10S and over to the Hemera from E3D. This is notable for me for a couple of reasons. First, the dual extrusion setup is less optimal than I liked, it worked most of the time but was always a hassle to get working properly and too many variable to go wrong.
Migrating to GKE For some time now I’ve been a fan of Kubernetes. I run a small cluster at home for tinkering, but it doesn’t really enable me to get a feel for running this in the cloud. I need to setup my own load balancer (metallb) storage is more annoying as I need to provide that as well (glusterfs). I have sorted those problems, but I still wanted to try running something in the cloud.