> ## Documentation Index
> Fetch the complete documentation index at: https://radarhq.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# GitOps integration coverage

> Exact CRD, API version, fleet, topology, detail, and structured AI coverage for Radar's Argo CD and Flux integrations.

This page is the implementation-level reference for Radar's Argo CD and Flux integrations. Start with the [GitOps workspace](/docs/features/gitops) for the shared workflow and controller capability comparison, or the [FluxCD integration](/docs/features/integrations/flux) for a screenshot-led Flux walkthrough and setup guidance.

## Flux CRDs

| CRD            | API version                              | Fleet | Topology | Detail    | Structured AI summary |
| -------------- | ---------------------------------------- | ----- | -------- | --------- | --------------------- |
| GitRepository  | `source.toolkit.fluxcd.io/v1`            | -     | Yes      | Dedicated | -                     |
| OCIRepository  | `source.toolkit.fluxcd.io/v1beta2`       | -     | Yes      | Dedicated | -                     |
| HelmRepository | `source.toolkit.fluxcd.io/v1`            | -     | Yes      | Dedicated | -                     |
| Bucket         | `source.toolkit.fluxcd.io/v1`            | -     | Yes      | Generic   | -                     |
| Kustomization  | `kustomize.toolkit.fluxcd.io/v1`         | Yes   | Yes      | Dedicated | Yes                   |
| HelmRelease    | `helm.toolkit.fluxcd.io/v2`              | Yes   | Yes      | Dedicated | Yes                   |
| Alert          | `notification.toolkit.fluxcd.io/v1beta3` | -     | -        | Dedicated | -                     |

Radar extracts failing `Ready`, `Healthy`, `Released`, and `TestSuccess` conditions, plus `Stalled=True` and `Reconciling=True` state, into issues. Kustomizations and HelmReleases support Reconcile, Sync with source, Suspend, and Resume.

Flux desired manifests are not currently available to Radar for Git-to-live field diffs. HelmRelease-managed resources also do not carry the client-side last-applied annotation that backs Radar's local diff fallback. See [#601](https://github.com/skyhook-io/radar/issues/601) for desired-state coverage work.

## Argo CD CRDs

| CRD            | API version            | Fleet | Topology | Detail    | Structured AI summary |
| -------------- | ---------------------- | ----- | -------- | --------- | --------------------- |
| Application    | `argoproj.io/v1alpha1` | Yes   | Yes      | Dedicated | Yes                   |
| ApplicationSet | `argoproj.io/v1alpha1` | -     | -        | Generic   | -                     |
| AppProject     | `argoproj.io/v1alpha1` | -     | -        | Generic   | -                     |

Application diagnosis includes operation failures, Application conditions, unhealthy or missing children, manual drift, and drift that persists after a successful automatic sync. Managed resources can include recent Kubernetes events and field-level drift.

Applications support Sync with options, Refresh, Hard refresh, Terminate, Suspend or restore auto-sync, Rollback, and Selective sync.

<Note>
  Field-level drift depends on desired-state availability. The local fallback requires `kubectl.kubernetes.io/last-applied-configuration`; server-side-applied resources do not carry that annotation. When configured, Radar's Argo CD API integration can retrieve Git-rendered desired state for canonical resource diffs.
</Note>

## Shared lifecycle and scope

For both controllers, Radar treats a resource with `metadata.deletionTimestamp` as terminating. It suppresses stale sync and health state, disables mutating operations, reports deletion age and finalizer ownership, and adds controller-health attribution when RBAC permits.

Topology is cluster-local. Radar can connect a GitOps parent to managed resources only when those resources are visible in the connected cluster. This is usually true for Flux. Argo CD hub-and-spoke deployments may show the Application without workload edges when the workloads live in another cluster.