Skip to main content
The Fleet section in the left rail rolls up data across every cluster in your org. It’s the answer to questions like “which of my clusters has audit failures right now?”, “which one is running an outdated version of cert-manager?”, or “where is this resource called payments-api?”. Radar Cloud fleet topology - aggregated multi-cluster view with per-cluster health and drift

​
Pages

​
Problems

/fleet/problems - cross-cluster grid of critical and warning conditions. Shows pods that aren’t ready, deployments that aren’t progressing, expired or expiring certs, and audit findings tagged severity=critical. Filterable by:
  • Cluster - subset to specific clusters.
  • Namespace - across all clusters.
  • Severity - critical / warning.
  • Category - workload / network / cert / audit / etc.
Click any row to drop into the resource in its cluster. /fleet/search - hero-style search bar, queries every connected cluster in parallel and merges results. Useful when:
  • You know a name (payments-api) but don’t remember which cluster it’s in.
  • You want to find every Ingress with a specific host.
  • You’re chasing a label across the fleet.
Result rows show the cluster as a chip; clicking opens that cluster’s resource browser.

​
Checks

/fleet/checks - the Cluster audit findings rolled up across the fleet. Useful for:
  • “Which cluster needs the most attention?” (sorted by failing count).
  • “Which check fires across the most clusters?” (sorted by check).
  • “Did the new policy land everywhere?” (filter by check ID, see which clusters still fail).

​
Packages

/fleet/packages - drift matrix for installed Helm releases (and any tools Radar has version metadata for, like Cilium / Argo / Karpenter / Linkerd). One row per package, one column per cluster, cells colored by version skew. Useful for:
  • “Are all clusters on the same cert-manager version?”
  • “Which clusters haven’t been upgraded to argocd:2.13?”

​
Performance

Fleet views fan out to every connected cluster in parallel. For ~10 clusters this is sub-second; for 100+ clusters expect a few-second initial load with progressive rendering as each cluster reports back. Disconnected clusters are shown with a not reporting chip - their data slot is empty until the in-cluster Radar reconnects.

​
RBAC

Fleet views are gated on the user’s Cloud role:
  • Viewer / member / owner all see fleet views for clusters they have access to.
  • “Access” means the cluster is in the org. There’s no per-cluster RBAC at the Cloud layer today - role gating happens inside the cluster via Cloud RBAC.
If you need per-cluster access control across the fleet (some users see prod, others don’t), use K8s impersonation: assign the cloud:viewer group to non-prod clusters’ bindings only and bind cloud:member only on the clusters where they should mutate.

​
What’s NOT here today

  • Cross-cluster topology. Each cluster’s topology is per-cluster. Fleet-wide topology (services that span clusters via mesh / Submariner / etc.) is on the roadmap.
  • Cross-cluster timeline. Same - per-cluster only today. The dashboard’s “recent problems” lane on the home page is the closest thing.

​
See also