Radar treats Argo CD and Flux CD as native, not as generic CRDs. You get a typed view of every Application / Kustomization / HelmRelease, the resources they manage, and one-click controls for the operations you’d otherwise run viaDocumentation Index
Fetch the complete documentation index at: https://radarhq.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
argocd / flux CLI.
Argo CD
| What | How |
|---|---|
| Applications list | Top-level GitOps view, filtered by sync / health / project |
| Sync status | Per-application: in-sync / out-of-sync / unknown |
| Health | Healthy / progressing / degraded / suspended / missing |
| Managed resources | The full inventory; click to drop into the resource browser |
| Sync | POST /api/argo/applications/{ns}/{name}/sync - manual, with optional prune / replace |
| Refresh | Force a re-fetch from the source repo |
| Suspend / resume | Toggle automated sync |
| Terminate | Cancel an in-flight operation |
| Revision history | Recent syncs with their git SHA and outcome |
Flux CD
| What | How |
|---|---|
| Kustomizations & HelmReleases | The two main reconciler kinds, listed with status |
| Sources | GitRepositories / OCIRepositories / HelmRepositories / Buckets |
| Reconcile | POST /api/flux/{kind}/{ns}/{name}/reconcile - request a single reconcile pass |
| Sync with source | Force the source to re-fetch first, then reconcile |
| Suspend / resume | Toggle automated reconciliation |
| Last applied revision | Shows the actual SHA / digest that’s running |
On the topology graph
Argo Applications and Flux Kustomizations / HelmReleases group their managed resources visually - you see the cluster of pods / services / configs the GitOps unit manages, with the controller as a parent node.In the timeline
Reconciliation events flow into the Timeline like any other K8s event, plus structured “applied / pruned / failed” entries with the diff of what changed.RBAC
Reading status only needs the default ClusterRole’s read access onargoproj.io / *.toolkit.fluxcd.io (enabled by default in rbac.crdGroups.argo / .flux).
Triggering sync / reconcile / suspend needs patch on the parent CRDs. The chart enables the right verbs when rbac.helm: true is set, or you can scope it more tightly via rbac.additionalRules.
See also
- Topology view - GitOps groupings.
- Resource browser - per-resource sync state chips.
- Integrations & CRDs - the full CRD list.