"Always remember to write down the steps taken to get the container working."

Hahaha, I want to highlight this, underscore it, and blow it up. Seriously. Writing down your debugging steps is crucial but it's not the first thing you think to do and you kick yourself later for not doing it.

I wrote this plugin to quickly diagnose pods that fail to start:

https://github.com/jpriebe/kubectl-dpod

It gives you container-level info, pod events, and logs from failed containers all in one quick view.

Very cool! I'll add this tool to the article

I love the debug script at the end. I can't tell you how many times I've manually installed vim and lsof when troubleshooting an issue.

> https://raw.githubusercontent.com/releaseapp-io/container-de...

I was a heavy user of k8s at a previous company. They had a very talented and decently sized devops team. They made my life as a customer very easy, so much so that I assumed I could just spin up k8s on my own for a side project. I was surprised how much work it was to get something online.

whats old is new again!

kube and dockerz have been huge for scaling apps but also have given us a new layer of opacity.

debugging and debugging tools are always The Coolest.

this isn’t a sexy stuff but eventually everyone runs into crashloop.

thanks for write up.

Kubernetes is hard, it's the simple stuff that we all need to know

True. You can't remove the complexity, you just move it to another layer. This is great... until the thing isn't working, then you have to debug on a whole different layer, in a completely different kind of way.

Debugging is truly an art