Cost & Rightsizing (Beta)

When OpenCost data flows from a cluster, a Cost tab appears for it. There is no new backend service to operate: the tab is a lens over cost metric families the agent ships into KubeBolt’s metrics store, scoped per cluster like everything else.

What the Cost tab shows

KPI strip — monthly spend run-rate, idle cost, available rightsizing savings, cost per pod, and efficiency.
Trends — spend run-rate and allocated-vs-total cost over the selected range.
Breakdown — cost by namespace, workload, and node, so “who is spending this?” is two clicks away.
Rightsizing recommendations, in money — the same recommendations the Capacity tab computes from real usage, priced per item.

When the underlying data window is younger than 2 days, rightsizing panels carry a Preliminary badge — treat those figures as directional, not a mandate.

Requirements

Agent 1.3.0 or newer (OpenCost sourcing shipped in that line).
OpenCost metrics reaching KubeBolt via one of the three modes below.

Three ways to connect OpenCost

Pick one in the Add Cluster wizard — it renders the final helm values:

1. Bundled by KubeBolt — the agent chart installs OpenCost as a sub-chart and scrapes it. Simplest path if you don’t run OpenCost today:

--set opencost.enabled=true

2. Scrape your existing OpenCost — you already run OpenCost; the agent scrapes its exporter. If the service name isn’t auto-derivable, point at it:

--set opencost.exporterUrl=http://opencost.opencost.svc:9003/metrics

3. Read from your Prometheus — your existing Prometheus already scrapes OpenCost; the agent reads the cost metric families through the same promRead connection used for metrics:

--set agent.promRead.enabled=true \
--set agent.promRead.cost.enabled=true \
--set agent.promRead.url=http://prometheus.monitoring:9090

The cost families involved are node_*_hourly_cost, container_*_allocation, and pv_hourly_cost — appended to the core KubeBolt metrics, never replacing them.