Radar

The MCP-for-AI-agents piece is the most interesting bit and the existing comments haven't poked at it. What can an agent actually do via Radar's MCP — read-only stuff (describe pods, fetch events, summarise an outage), or destructive ops (kubectl delete, rollout restart)? That boundary decides whether anyone runs this against a prod cluster.

Looks very useful, sharing it with my team

Was actually just looking for sth like this. Was about to build an internal shoddy version, this will do!

nice - gave it a star! good luck!

Local-first with zero cluster-side installation is the right call. When I was scaling an engineering org from 15 to 120, the biggest friction with K8s tooling was always the chicken-and-egg problem: you need cluster access to install the tool that helps you understand the cluster. Having this run as a single binary using existing kubeconfig means any engineer can get visibility without needing platform team approval first. That alone probably saves a week of onboarding time per new infrastructure hire.

a cluster audit with 31 checks across security and reliability is a massive value-add for day-to-day ops. we usually run separate trivy or kyverno reports, so having that integrated into the primary ui workflow is a huge time-saver. does the audit allow for custom check injection? @nadav_erell

Hey PH 👋 Eyal, Roy, and Nadav here - the team behind Radar. We also build Skyhook, YC W23.We've wanted a better Kubernetes UI for a long time. kubectl is powerful, but day-to-day cluster work still ends up split across terminals, dashboards, Helm, Argo/Flux, cloud consoles, and log tools.The existing options all have tradeoffs. Lens lost the OSS trust that made people love it. FreeLens is a welcome fork, but still carries the same heavy Electron desktop model. Headlamp is useful, but shallow once you want deeper operations - Helm, GitOps, traffic, audits. k9s is excellent if you live in the terminal, but not everyone does. And the SaaS tools often price by node and ask for a work email before they let you look at your own cluster.So we built the Kubernetes UI we wanted: fast, local-first, open source, and not locked behind an account. We quietly shipped it a couple of months ago. The community took it past 1.4k GitHub stars and gave us way more feedback than we expected, so we kept shipping. Today is the proper launch.What's in it:- Topology with real ownership chains, not force-directed spaghetti- Live event stream across all resources using Kubernetes watches, not polling- Helm release management with diff/rollback + native Argo CD / Flux sync- Live traffic flows via Hubble/Cilium, Caretta, or Istio- Cost insights via OpenCost - auto-detected per namespace, workload, and node- Cluster audit - 31 checks across security, reliability, and efficiency- Image filesystem viewer - read container files in the UI, no exec, no pull- Built-in MCP server - point Cursor or Claude at your clusterPlus first-class integrations for 20+ popular K8s tools - Argo Rollouts, Karpenter, KEDA, cert-manager, Trivy, Kyverno, Velero, Knative, and more.Single Go binary. Apache 2.0. No account required. No usage tracking. No cloud dependency.Site: https://radarhq.ioRepo: https://github.com/skyhook-io/radarDiscord: https://radarhq.io/community/chatAlso yes, we cared about making it beautiful. K8s tools don't have to look like punishment.Would love your feedback - what's missing, what breaks, what we got wrong. We're here all day.