Skip to main content
If OpenCost is installed, Radar shows current and historical Kubernetes allocation cost from your existing Prometheus. The integration is passive and read-only.

​
What you see

  • Cluster cost - current hourly rate, monthly projection, and CPU, memory, storage, and network breakdowns when available.
  • Namespaces - sortable cost rows with workload details on demand.
  • Workloads and applications - focused CPU and memory allocation cost for Deployments, StatefulSets, and DaemonSets.
  • Nodes - instance, region, and hourly or monthly pricing where provider data is available.
  • Trends - historical allocation cost over 6h, 24h, or 7d with hover details.
  • Allocation use - CPU and memory shown separately when complete usage evidence is available.
Radar presents monthly projections from the current hourly rate. Historical spend uses the selected range.

​
Request guidance

The workload Cost tab can also show Rightsizing. Rightsizing uses Prometheus demand evidence to evaluate one workload’s configured requests. It is separate from OpenCost allocation accounting and does not claim guaranteed savings.

​
How it auto-detects

Radar discovers Prometheus automatically or uses the --prometheus-url override. Cost views become available when the required OpenCost allocation metrics are queryable.

​
Common gaps

Some cost categories require additional OpenCost configuration:
  • GPU pricing - requires GPU pricing data.
  • Cloud egress - requires cloud-provider integration.
  • Persistent volumes - requires storage-class pricing.
  • Spot vs. on-demand - requires provider and node metadata.

​
Limitations

  • Radar does not change requests, instance types, or running workloads.
  • Workload and application cost currently focus on steady-state Deployment, StatefulSet, and DaemonSet workloads.
  • Batch workload, storage, and network attribution may remain at namespace or cluster level.
  • OSS cost data is per cluster. Radar Cloud provides fleet views.

​
See also