Radar crossed 3,000 stars on GitHub!
Thank you to everyone who starred, forked, filed an issue, or sent a PR! 37 contributors and counting.
If you haven't tried it yet:
brew install skyhook-io/tap/radar
https://t.co/i5BJjBhxQu
Reachability is in Radar OSS.
Install: brew install skyhook-io/tap/radar
Open any Service → Reachability.
Eyal’s write-up covers the mechanism, reproducibility and current limits:
https://t.co/15qbcR2Hte
1/
Kubernetes says everything looks healthy: Deployment 2/2 Ready, Service has endpoints, Ingress has an address.
But traffic still doesn’t arrive.
The problem is often not one broken object. It is the path between them.
5/
Example: the API-server relay returns 200.
That still does not prove real application traffic can reach the Service. A NetworkPolicy may treat that path differently.
Radar reports: “Reached via API server - not live traffic.”
The full essay by Roy Libman surveys where real tools sit on the ladder today and ends with a 30-minute exercise to run with your team: https://t.co/p2UjiJ8rAb
The kubelet already restarts containers at 3am without asking anyone. Kubernetes is full of automation like that. AI agents add something different: judgment. Our CPO wrote a framework for deciding how much judgment to delegate.
Levels attach to verb-environment pairs, never to agents. "Restart pods in staging" and "delete PVCs in prod" can sit four levels apart under the same agent on the same cluster.
Radar is a portable Kubernetes interface that runs as a single binary from your laptop, offering topology, resource, and traffic visualization along with MCP support for AI agents.
https://t.co/W2qsKua7Pv
a config change that never emitted a Kubernetes event, caught anyway
one minute: the crashloop still on the record, then the field diff showing what the value was before someone changed it
https://t.co/K0zK5ZRile
verdicts carry evidence and a confidence band. inconclusive is a real answer. an all-clear means it went and checked.
apache-2.0, single binary. https://t.co/0yhabRBHZ4
your deployment is 0/1 and kubectl logs gives you nothing.
correct. there is no pod. admission rejected it, and the reason is sitting in a controller status you have not opened.