# Kubernetes Cost Allocation

Kubernetes environments are shared by nature.

Native cloud tags are insufficient.

OneLens K8s agent collects telemetry:

* CPU usage
* Memory usage
* Storage usage
* Network usage

Costs are attributed at:

* Namespace level
* Workload level
* Pod level (where applicable)

Then mapped to cost centres.

***

### How It Works

```
Cluster Cost
     ↓
Namespace Usage
     ↓
Workload Attribution
     ↓
Cost Centre Mapping
```

This enables:

* Team-level cluster accountability
* Workload-level optimization
* Shared cluster fairness


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onelens.cloud/observe-visibility-and-insights/cost-allocation/virtual-tags/kubernetes-cost-allocation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.