Cluster costs
Preview
This guide describes an intended experience that is not generally available. The screenshots use sample data. Workflows, labels and availability can change before release.
Kubernetes cost management would allocate cluster spend to namespaces and workloads (OpenCost-style), including idle capacity.
This is not a Harness Cluster Orchestrator or CloudHealth Kubernetes reports replacement. It is Preview. Do not lead a procurement conversation with cluster cost until it is generally available. Platform teams should start with Cost Explorer on the node’s cloud bill.

Intended workflow
- Connect a cluster after the cloud billing connector is healthy.
- Wait for the first allocation window (often 24 hours).
- Open namespaces, then workloads.
- Send idle capacity to Resource scheduling or a recommendation.
Until this ships, Kubernetes nodes still appear as ordinary compute in Cost Explorer.