Skyhook Radar
Each find is an event on the cluster, and Radar confirms it in the lens.
What we built
Every distance alert becomes a Kubernetes Event, so Skyhook Radar's timeline of the cluster shows each find as it happens, and Radar confirms the alert back to the people looking. In the lens a confirmed alert carries a small RADAR eyebrow; on the live map, a Radar strip shows how many alerts were mirrored and the last one.
How it works
- Skyhook Radar 1.20.2 runs in the namespace
save-the-world-radar, read-only over the org's namespaces. - The Radar bridge, a single Node script in a ConfigMap, polls influence-api's
GET /api/alertsevery 2 s and writes each new alert as a core/v1 Event: reasonHeroCloser,HeroFound,HeroFartherorHeroLost(Warningfor lost), sourceinfluence-radar-bridge. Each Event is named after its alert, so a repeat after a restart is a 409, never a second Event. - After every poll the bridge posts its heartbeat,
{mirrored, lastEvent}, toPOST /api/integrations/radar. - Radar 1.20.2 has no alert rules of its own (that is a Radar Cloud feature), so the bridge reads Radar's
/api/eventsand confirms each alert from it: the API sends the alert again with the same id,source: 'radar', and Radar's reason and event id. The lens and the map show it as confirmed.
In the code
influence-api/deploy/radar-bridge/README.mdandinfluence-api/deploy/radar-bridge/radar-bridge.yaml: the bridge, its Role and how to apply it.hero-goggles/src/alerts.js: what a Radar-confirmed alert looks like.hero-goggles/src/LensAlert.jsx: the lens's alert band and its RADAR eyebrow.hero-goggles/src/live/Integrations.jsx: the Radar strip on the map.
Status
Live Radar and the bridge were installed by hand on 9 November 2026 and are annotated as temporary. Not live Radar's own public address, behind basic auth, is not served yet: a ListenerSet on the edge answers, but through the tunnel the host lands on the wildcard listener. Until that is fixed, Radar is reached from inside the cluster.