> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/integrations/kubernetes.md).

# Kubernetes

OneLens can be integrated with your selected K8s clusters to get usage and cost insights, all in one place. This will help you gain control over cost and run clusters efficiently.

OneLens supports Kubernetes integration for EKS *(Amazon Elastic Kubernetes Service on AWS),* AKS *(Azure Kubernetes Service on Azure)* and GKE (Google Kubernetes Engine on GCP)

Follow the guidelines in order to complete the setup:

### [Agent Setup](/integrations/kubernetes/onelens-agent.md)

Set up the OneLens K8s agent using Helm to start collecting resource usage and metadata from your cluster.

### Cost Allocation Setup

Enable cloud-specific cost allocation so OneLens can break down cluster spend. Complete the steps for your cluster's cloud.

#### AWS

[**Enable Split Cost Allocation for EKS**](/integrations/kubernetes/enable-split-cost-allocation-for-eks.md) - enable workload-level cost allocation by linking your EKS resource usage with your CUR report.

#### GCP

[**Enable Cost Allocation for GKE**](/integrations/kubernetes/enable-cost-allocation-for-gke.md) - enable pod-level cost allocation on your GKE clusters.

[**Create a GCP API Key for Pricing Data**](/integrations/kubernetes/onelens-agent/create-gcp-api-key-for-pricing-data.md) - create the API key OpenCost uses to fetch GCP public pricing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onelens.cloud/integrations/kubernetes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.