Kubernetes cost by team
Cluster cost per namespace and team
A cluster's bill names nodes, not the teams that run workloads on them. The agent sends the labels that name a team, a virtual tag turns them into one value, rules assign each namespace to a segment, and a saved report shows every team what its namespaces cost.
Permanent Free plan with no time limit
The cluster gap
Nodes are billed, teams are not
The invoice stops at the node
The cloud provider bills the instances a cluster runs on. Which namespace used them, and which team owns the namespace, is nowhere on the bill.
Labels disagree
The team label sits on some pods and some namespaces, under more than one spelling, and some namespaces carry none at all.
Idle capacity has no owner
Capacity no workload uses still costs money, and without a rule it belongs to no team.
In the product
From labels to a report per team
An agent in the cluster
The agent sends the pod and namespace labels you allow. Each reaches reports as a tag, every row carries the cluster, namespace and node, and cost appears the morning after the install.
Nodes priced from the cloud bill
Nodes take their price from the AWS, Azure or Google Cloud connection that pays for them, or from rates you set. A node without a price is counted as unpriced, shown in the cluster's status, and appears in no namespace.
One team tag from many labels
A virtual tag reads the team label first and your other spellings after it, and a rule per unlabelled namespace fills the gaps. Its preview shows what stays unmatched.
Namespaces assigned to segments
One segment per team, with a rule on its namespaces or on the team label. Idle cost sits in its own namespace: a rule can assign it to a platform segment, or it stays visibly unallocated.
A report per namespace and team
Group by namespace or by the team tag, add the cluster when there are several, and schedule a copy filtered to each team, weekly.
Related pages
- Kubernetes integration
How the agent reports and how a cluster's cost is calculated.
- Cost allocation
Segments and ordered rules for every provider, not only the cluster.
- The Kubernetes cost by team guide
Step by step in the product, on the documentation portal.
Show each team what its namespaces cost
Install the agent on the permanent Free plan and report cluster cost per namespace and team.
Permanent Free plan with no time limit