> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Kubecost (IBM / Apptio) as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/kubecost

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Kubecost (IBM / Apptio) connector syncs allocation by namespace, allocation by controller, allocation by pod, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

Connect your Kubecost deployment to pull Kubernetes cost allocation and infrastructure asset costs.

Enter the URL where your Kubecost cost-model API is reachable (e.g. `https://kubecost.example.com` - with or without the `/model` suffix). Self-hosted Kubecost ships with no built-in auth, so the API must be exposed to PostHog, typically behind an ingress or auth proxy. If your deployment or proxy requires a token (e.g. Kubecost Cloud), provide it as the API key and it is sent as a bearer token - this requires an `https://` URL so the key is never sent in plaintext.

You'll be asked for:

-   **Kubecost API URL**: for example `https://kubecost.example.com`.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Kubecost (IBM / Apptio) tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Kubecost API URL` | text | Yes |
| `API key (optional)` | password | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `allocation_by_namespace` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by namespace — one row per namespace per day. | Incremental, Full refresh | window\_start | — |
| `allocation_by_controller` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by controller — one row per controller per day. | Incremental, Full refresh | window\_start | — |
| `allocation_by_pod` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by pod — one row per pod per day. | Incremental, Full refresh | window\_start | — |
| `allocation_by_cluster` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by cluster — one row per cluster per day. | Incremental, Full refresh | window\_start | — |
| `allocation_by_node` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by node — one row per node per day. | Incremental, Full refresh | window\_start | — |
| `allocation_by_service` | Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by service — one row per service per day. | Incremental, Full refresh | window\_start | — |
| `assets` | Cluster infrastructure costs from the Kubecost Assets API — one row per asset (node, disk, network, load balancer, cluster management fee) per day. | Incremental, Full refresh | window\_start | — |
| `cloud_costs` | Cloud provider billing costs (e.g. AWS CUR, Azure, GCP billing export) from the Kubecost Cloud Cost API, covering spend inside and outside Kubernetes — one row per billing line item per day. | Incremental, Full refresh | window\_start | — |

## Troubleshooting

-   If the connection fails with an authorization error, the API key (optional) is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.