User has developed a tool that highlights bottlenecks and causes in Kubernetes debugging and is seeking feedback for further improvements and features.
Kubernetes people, We all love kubectl apply and watching things scale, but the debugging part… ouch. My personal least favorite: when a pod is slow or failing, and you have to chain kubectl describe, logs, events, top, exec into containers, grep across namespaces, etc. — just to find out it's a connection pool exhaustion or a retry loop in a dependency. After too many of these sessions, I quietly hacked together a little tool that tries to ingest logs/traces and automatically highlight the bottleneck + cause + possible fix. Still rough, but it already cuts down the hunting time for me. What's the Kubernetes debugging task that makes you want to throw your laptop out the window? And how do you usually tackle it?