CrashLoopBackOff is one of the most common failure states in Kubernetes and the root cause often isn’t obvious from logs alone (not for me atleast ).

So I vibe-coded [CrashLoop Analyzer](https://crashloop-analyzer.vercel.app) a fast, browser-based tool where you paste your `kubectl logs` or `kubectl describe pod` output and get a likely root cause.

It currently catches common failure patterns like: - ImagePull errors - OOMKilled containers - Volume mount/setup issues - Failing probes

No AI. No backend. No login. Just plain JavaScript and a bunch of pattern matching.

---

Thinking of adding: - Visual analysis mode - Log history or team storage

Would love to know if that's something you'd actually use or if you have patterns I should add.

[Live demo](https://crashloop-analyzer.vercel.app) [Source code](https://github.com/MorrisLaw/k8s-crashloop-analyzer)

Appreciate any feedback. – Jeremy