Skip to content
All releases
feat
(8mo ago)

Shipped by

  • Ugurcan CaykaraUgurcan Caykara

Cost Attribution Rules: Assign New Workloads Automatically

Define rules once and Cost Attribution assigns new workloads, namespaces and volumes to the right team or department as they appear.

Manual attribution doesn't scale

Cost attribution is only useful when it's complete. But clusters don't hold still — new workloads deploy, namespaces get created, volumes get provisioned. Every one of them starts out unattributed, and someone has to go map it to a team or department by hand. Miss a few and your rollups drift out of date.

Kubeadapt now lets you write rules in Cost Attribution so you don't have to do that by hand anymore.

Set the rule once, new entities route themselves

Instead of attributing every workload, namespace, and PV yourself, you define matching rules in Cost Attribution. When new entities are deployed in your environments, Kubeadapt evaluates them against your rules and assigns them automatically — no manual mapping, no catch-up passes.

The result: your Department > Team > Namespace > Workload hierarchy stays complete on its own, even as the cluster changes underneath it.

How it fits with what you already have

This builds directly on Teams & Departments. You still get automatic assignment from Kubernetes team and department labels, and you can still assign anything from the dashboard by hand. Rules add a third path: a standing policy that keeps the long tail attributed without either labels or clicks.

  • Labels handle workloads that already carry them.
  • Manual assignment handles one-off exceptions.
  • Rules handle everything new, automatically.

Getting started

Go to Cost Attribution and open Rules. Create a rule, point it at a team or department, and new matching entities will be assigned as they appear. For how attribution and rollups are calculated, see Cost Attribution.