Redis Radar release notes 2026.9.5
Connect clusters that Radar can't reach directly by installing an agent.
| Redis Radar |
|---|
Radar can now collect from clusters it can't reach directly. You install an agent on a host inside the network that holds them, and the agent opens an outbound connection to Radar.
This is a Short-Term Support (STS) release. See Self-managed releases for more details.
Highlights
Connect clusters with an agent
- Collect from Redis Software and Redis Open Source clusters behind a firewall, in a private subnet, or on a segmented network. Radar needs no inbound access to your network.
- Choose between two modes. Managed agents receive source credentials from Radar, so you add and change sources from the Radar UI. Static agents read their sources from a file on the agent host, so those credentials never leave it.
- Collect from a fully isolated network by exporting to a file on one host and submitting it from another.
- Install from standalone agent packages for Linux on amd64, including Federal Information Processing Standards (FIPS) 140-3 builds.
- Track every agent under Settings > Agents and in the Connected agents list on the Connections page, with its mode, platform, version, and last heartbeat.
Radar accepts agent connections on its agent gRPC endpoint, which isn't enabled on every Radar deployment. See Connect clusters with an agent.
Downloads
- Helm chart:
radarversion2026.9.5, from the Redis Helm repository athttps://helm.redis.io/radar
Container images
The Helm chart pulls these images from Docker Hub. For an air-gapped install, mirror each one to a registry your cluster can reach.
- API server:
redislabs/radar:app-v2026.9.5 - Worker:
redislabs/radar:worker-v2026.9.5 - Migration job:
redislabs/radar:migrate-v2026.9.5 - Database wait and Helm test:
library/busybox:1.37 - Bundled PostgreSQL, only if you enable it:
library/postgres:18.4-bookworm
The Radar images are built for linux/amd64 only.