Hadi Farnoud

Hey Product Hunt folks,

I'm building KubeAgent, a CLI for Kubernetes teams who are tired of finding out about cluster issues only after something is already on fire.

The idea is simple: run `kubeagent onboard` once to scan your cluster and build a local knowledge base, then run `kubeagent watch`. When something looks wrong, KubeAgent checks logs/events/describes, tries to explain the likely root cause, and suggests a fix. Safe actions like pod restarts can be applied automatically; risky actions wait for human approval through Slack, PagerDuty, Discord, Teams, Telegram, or a webhook.

I'm building it because I wanted something between "another alert in a dashboard" and "give an AI agent full access to prod." The hard part has been drawing the safety line clearly enough that it can be useful without being reckless.

Last week one of our web pods restarted 11 times in 24 hours, and another restarted 9 times. The app worked, users were happy, and latency was fine. Our application logs had nothing to say about it, just gaps where a process used to be.

We spent a couple of days chasing the wrong thing. Then we found a Kubernetes default we d never thought to override, and the crash loop stopped.

Hey everyone!

I love the concept of "vibecoding", getting into the flow, using AI to build fast, and focusing purely on the product. But for a lot of developers (especially in emerging markets like Indonesia), that vibe instantly dies when it's time to deploy.

Suddenly, you are dealing with complex server setups, fighting DevOps configurations, or getting blocked because you don't have an international credit card to spin up a basic server.

Deployment shouldn't ruin the vibe. It should be just as seamless as writing the code.