Kubernetes Agent
A lightweight in-cluster agent that collects cost and utilisation attribution and pushes it outward — no inbound cluster access required.
At a glance
| Form | A containerised agent, deployable through standard Kubernetes manifests |
| Audience | Infrastructure — platform teams running Kubernetes |
What it is
A lightweight agent deployed inside your Kubernetes cluster that collects cost and utilisation attribution and pushes it to the platform — providing an alternative to Kubecost or OpenCost.
Who it is for
Platform teams wanting Kubernetes cost attribution without deploying and operating a full cost-monitoring stack.
How it works
Push, not poll
Because the agent pushes rather than being polled, it works without granting the platform inbound access to your cluster — an important property for clusters behind private networking.
Features
- Containerised, deployable through standard Kubernetes manifests
- Namespace, workload, and container-level cost and utilisation collection
- Push-based delivery requiring no inbound cluster access
- An alternative to Kubecost and OpenCost rather than a dependency on them
- Feeds the same thirteen Kubernetes detectors as the other ingestion paths
How to use it
Enable Kubernetes ingestion
In Integrations, and obtain the workspace ingestion credential.
Deploy the agent into the cluster
With that credential configured.
Confirm snapshots are arriving
In the Kubernetes module.
Map namespaces to teams
To make cluster cost chargeable. See Cost Allocation and Ownership.
Work the resulting findings
Rightsizing and idle-pod findings appear in Opportunity Queue alongside every other provider.
Why it matters
Kubecost and OpenCost are capable, but they are themselves systems to deploy, operate, and upgrade — a real barrier for teams whose problem is a lack of platform capacity in the first place.
A minimal push agent makes cluster cost attribution available without that overhead, and push delivery avoids the network exposure that pull-based collection would require.
Connects to
- One of three ingestion paths for the Kubernetes module
- Configured in Integrations
VS Code Extension
Inline Terraform cost hints while infrastructure code is being written — the earliest possible point of cost feedback.
Public Surfaces
Routes deliberately reachable without a session — savings previews, live detection coverage, tokenised dashboard sharing, and the public vendor directory.