> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Komodor as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/komodor > **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 - [Adding a data source](#adding-a-data-source) - [Available tables](#available-tables) - [Configuration](#configuration) - [Supported tables](#supported-tables) **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 Connect your Komodor account to sync Kubernetes services, jobs, clusters, and monitors into the PostHog data warehouse. ## Adding a data source 1. Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog. 2. Click **\+ New source** and then click **Link** next to Komodor. 3. In Komodor, go to **User settings > API Keys** and create a new API key. Grant read access for the tables you want to sync. 4. Back in PostHog, select your **region** (US or EU), enter your **API key**, then click **Next**. 5. Select the tables you want to sync, set the sync frequency, then click **Import**. Once the syncs are complete, you can start using Komodor data in PostHog. ## Available tables | Table | Description | Sync method | | --- | --- | --- | | `services` | Kubernetes services with their health status, latest deployment, and latest issue | Full refresh | | `jobs` | Kubernetes jobs and cron jobs with their status and issue details | Full refresh | | `clusters` | Kubernetes clusters connected to Komodor | Full refresh | | `monitors` | Monitor configurations used to detect failures in Kubernetes infrastructure | Full refresh | All tables use **full refresh**, meaning all data is reloaded on each sync. ## Configuration | Option | Type | Required | | --- | --- | --- | | `API key` | password | Yes | | `Region` | select | Yes | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `services` | Kubernetes services with their health status, latest deployment, and latest issue. | Full refresh | — | — | | `jobs` | Kubernetes jobs and cron jobs with their status and issue details. | Full refresh | — | — | | `clusters` | Kubernetes clusters connected to Komodor. | Full refresh | — | — | | `monitors` | Monitor configurations used to detect failures in Kubernetes infrastructure. | Full refresh | — | — |