Kubecano

Hey Indie Hackers! 👋

I’m a DevOps engineer with 15 years of experience, and for the last 7-8 years, I’ve been deep into Kubernetes. I’ve supported countless developer teams deploying their services on Kubernetes, and one thing I’ve seen over and over is how confusing and incomplete alerts from AlertManager can be – even for experienced DevOps engineers.

⚡ Why I Built It
I know firsthand how frustrating it is to figure out what’s really going on when an alert pops up or when a developer is stuck wondering why their application won’t start or keeps crashing. Kubernetes errors can be cryptic, and understanding them often means digging through logs, events, and manifests.

That’s why I started building Kubecano – to simplify incident management in Kubernetes:
✅ It enriches alerts with logs, events, and relevant manifest details – like showing the exact Java exception causing a CrashLoopBackoff.
✅ AI translates complex, technical alerts into clear, human-readable explanations.
✅ It suggests next steps or fixes with runbooks, guiding you through troubleshooting.

🛠 Where We Are Now
Right now, Kubecano is in the design phase and we’re just getting started on the MVP. We’re building a tool that I wish I had when supporting developer teams, and we’re excited to see how it can help others too.

🚀 Join the Journey
We’re building this with the community in mind, and we want your feedback! We’re setting up a waiting list for early adopters. If you sign up, you’ll get updates on our progress, opportunities to shape the product, and an invite to the closed testing phase.

🔗 Join the waiting list here: kubecano.com

Would love to hear your thoughts and connect with anyone facing the same pain points!