Hero Gogglesdocs byDarkshift

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

  1. Skyhook Radar 1.20.2 runs in the namespace save-the-world-radar, read-only over the org's namespaces.
  2. The Radar bridge, a single Node script in a ConfigMap, polls influence-api's GET /api/alerts every 2 s and writes each new alert as a core/v1 Event: reason HeroCloser, HeroFound, HeroFarther or HeroLost (Warning for lost), source influence-radar-bridge. Each Event is named after its alert, so a repeat after a restart is a 409, never a second Event.
  3. After every poll the bridge posts its heartbeat, {mirrored, lastEvent}, to POST /api/integrations/radar.
  4. Radar 1.20.2 has no alert rules of its own (that is a Radar Cloud feature), so the bridge reads Radar's /api/events and 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

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.