Integrations

Radar detects ecosystem tools at runtime. For CRD-backed tools, installing the CRD activates the matching renderer - typed detail views, smart columns in the resource browser, topology edges, AI-summary support, and the right action buttons (sync, suspend, rollout, restore). Data-source integrations use their own discovery, such as Prometheus Services or a Kubecost Aggregator. Every integration on this page is compiled into the binary; no plugins are required. Some remote or authenticated data sources require an endpoint or credentials. (New to Radar? Start with the product tour.)

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 Kubernetes, Cilium, and Calico policies, including staged-policy previews and workload coverage. Hubble-correlated denied flows in the traffic view.

Live traffic providers

Hubble (Cilium) and Caretta auto-detected for live request flows. Opens 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).

GPU & AI/ML

Dynamic Resource Allocation

ResourceClaims with allocation lifecycle (incl. leaked-device warnings), DeviceClasses, ResourceSlice device inventory, Pod-to-claim relationships.

NVIDIA GPU Operator

ClusterPolicy operator state and component rollout, NVIDIADriver lifecycle, MIG strategy.

AI/ML Ecosystem

Basic support for Kueue, KubeRay, KServe, Volcano, KAI, KAITO, NVIDIA NIM, Kubeflow training, AMD GPU Operator, and more - 37 kinds across 12 tools.

Cost & observability

OpenCost + Kubecost

Powers the Cost view from OpenCost-compatible Prometheus metrics or a Kubecost 3 Aggregator.

Prometheus Operator

Prometheus, ServiceMonitor, PodMonitor, AlertmanagerConfig. Auto-discovered cluster Prometheus powers latency percentiles in the Traffic view and OpenCost-compatible data in the Cost view.

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.

Infrastructure & data

Crossplane

Managed resources for every provider (Upbound AWS/GCP/Azure, provider-kubernetes, provider-helm, any community provider); Composite / Claim views with a per-resource live status badge on every composed resource; Compositions, CompositionRevisions, XRDs; upstream cloud errors surfaced verbatim.

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

	Radar	Plugin-based UIs
AI / MCP context	Every integration in the same context window	Each plugin emits its own (or doesn’t)
Update cycle	One binary version pin	N plugins, N pinned versions, N upgrade paths
Argo, Flux, Helm	Built-in	Install plugin
Live traffic, cost, Trivy, Kyverno	Built-in	Install plugin per provider

Topology

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

Traffic view

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

Cost view

OpenCost- or Kubecost-powered spend by namespace, workload, and node.

In-cluster RBAC opt-ins

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

​GitOps & rollouts