All figures are estimates, derived from on-demand and spot pricing for the resources Ankra can see. They are designed for trend-watching, right-sizing, and chargeback - not for reconciling a cloud invoice to the cent.
How it works
To estimate cost for a cluster, Ankra needs three things:- A cloud credential for the cluster’s provider (for example AWS or GCP), so it can resolve instance and volume pricing. See Credentials.
- The cluster to be online, so the agent can sync the current nodes and volumes.
- Pricing for the region and instance types in use.
Readiness states
The per-cluster cost view reports a readiness state so you always know why an estimate is or isn’t available:| State | Meaning |
|---|---|
ready | A cost estimate is available |
no_credential | No cloud credential is attached for this provider |
unsupported_provider | The cluster’s provider isn’t supported for cost estimation |
cluster_offline | The cluster is offline, so inventory can’t be synced |
awaiting_nodes | Waiting for the first node inventory sync |
awaiting_pricing | Nodes are known, pricing is still resolving |
estimate_pending | Inventory and pricing are present; the first estimate is being computed |
Per-cluster cost
Open a cluster and select the Cost view to see its estimate. It includes:- Summary - hourly cost, estimated monthly cost, month-to-date, and a projected month-end total, with a confidence level.
- Breakdown - compute split into on-demand and spot, plus storage, network, and control-plane cost, along with idle and unallocated portions.
- Coverage - how many nodes and volumes were priced. If some couldn’t be priced, the estimate is flagged as
coverage_incompleteso you know it understates the true figure. - Per-namespace allocation - cost allocated to each namespace (and the owning stack, where known) by CPU and memory share, so you can attribute spend to teams or workloads.
- Trend - a daily series of the monthly cost estimate so you can spot changes over time.
Fleet summary
The organisation-wide rollup aggregates every cluster’s estimate into a single number, with breakdowns by provider and a list of your top-spending clusters:Settings
Organisation admins can tune how cost is displayed and estimated under cost settings:| Setting | Description |
|---|---|
currency | Display currency: usd, eur, or gbp |
effective_discount_pct | A flat discount (0-100) applied to list pricing, to approximate committed-use or enterprise agreements |
include_network_egress_estimate | Whether to add an estimated network egress component |
Prerequisites checklist
Attach a cloud credential
Add an AWS or GCP credential for the cluster’s provider under Credentials.
Bring the cluster online
Ensure the agent is connected so node and volume inventory can sync.
Set your currency and discount
As an org admin, set the display currency and any committed-use discount in cost settings.