Skip to main content
Radar detects ecosystem tools at startup by listing CRDs in your cluster. If the CRD is installed, the matching renderer activates - typed detail views, smart columns in the resource browser, topology edges, AI-summary support, and the right action buttons (sync, suspend, rollout, restore). Every integration on this page is compiled into the binary; nothing to install, nothing to configure.
  • Graceful degradation. Missing RBAC for a CRD: the panel shows a “needs read on argoproj.io/applications” hint, not a blank page. Missing CRDs entirely: the integration is silently skipped.
  • No version handshake. Radar reads the schema, not a hand-written client. New CRD versions land in upstream releases without a Radar update.

GitOps & rollouts

GitOps (Flux + Argo CD)

Argo Applications and Flux Kustomizations / HelmReleases / Git & OCI repositories. Sync, suspend, refresh, terminate; managed-resource inventory; topology grouping per app.

Argo Rollouts

Rollout strategy, current revision, traffic split, pause / resume.

Argo Workflows

Workflow status, step graph, retry / suspend / resume.

Networking & service mesh

Gateway API

Gateways, HTTPRoutes, TLSRoutes, GRPCRoutes, TCPRoutes - typed views and topology edges.

Istio

VirtualServices, DestinationRules, traffic edges, mTLS scope.

Traefik

IngressRoutes, Middlewares, TLSStores.

Contour

HTTPProxies and policy attachments.

Network Policies

Native NetworkPolicy plus Cilium’s CiliumNetworkPolicy + CiliumClusterwideNetworkPolicy. Coverage card on the dashboard. Hubble-correlated denied flows in the traffic view.

Live traffic providers

Hubble (Cilium) and Caretta auto-detected for live request flows. Detail on the Traffic view.

Capacity & autoscaling

Karpenter

NodePools, NodeClaims, EC2NodeClass / AKSNodeClass / GCPNodeClass, full provisioning chain in topology.

Cluster API (CAPI)

Declarative cluster lifecycle. Cluster, ClusterClass, KubeadmControlPlane, MachineDeployment, MachineSet, Machine - with infrastructure-provider renderers.

KEDA

ScaledObjects + ScaledJobs, current scale, triggers.

Vertical Pod Autoscaler

VPA recommendations vs. live requests/limits, mode (off/initial/auto/recreate).

Cost & observability

OpenCost

Powers the Cost view - by namespace, workload, node.

Prometheus Operator

Prometheus, ServiceMonitor, PodMonitor, AlertmanagerConfig. Auto-discovery of cluster Prometheus for traffic/metrics.

Security & policy

Trivy Operator

VulnerabilityReports + ConfigAuditReports inline on every workload.

Kyverno

Policies, ClusterPolicies, PolicyReports - violations attached to the resources they’re failing on.

cert-manager

Certificates, Issuers, ClusterIssuers, expiry tracking.

Sealed Secrets

SealedSecret browse, decrypted-Secret link, status conditions.

External Secrets Operator

ExternalSecrets, SecretStores, ClusterSecretStores - sync state and provider config.

Data & lifecycle

Velero

Backups, Restores, Schedules - with restore actions in-line.

CloudNativePG

Clusters, Poolers, Backups; primary / replica visibility.

Knative

Serving (Service / Route / Configuration / Revision) and Eventing (Broker / Trigger).

Unrecognized CRDs

Any CRD not listed above still appears in the resource browser under its generic API group, with full YAML in the detail drawer. You don’t get a typed renderer or topology edges; you keep search, filter, and edit. To add a typed renderer for a CRD family Radar doesn’t yet know, see the contributor guide.

Compared to plugin-based UIs

RadarPlugin-based UIs
AI / MCP contextEvery integration in the same context windowEach plugin emits its own (or doesn’t)
Update cycleOne binary version pinN plugins, N pinned versions, N upgrade paths
Argo, Flux, HelmBuilt-inInstall plugin
Live traffic, cost, Trivy, KyvernoBuilt-inInstall plugin per provider

See also

Topology

Where most integrations express themselves visually - typed nodes and edges per CRD family.

Traffic

Hubble / Caretta / Istio auto-detection and the live edge overlay.

In-cluster RBAC opt-ins

The Helm rbac.crdGroups block - what each integration needs read access to.