Skip to main content
Telara

Integrations / Kubecost

Kubecost logo

Kubecost

Kubecost Kubernetes cost monitoring for allocation, assets, cloud cost, efficiency, savings, and cluster spend analysis.

API key
Indexes
Actions

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Kubecost (or OpenCost) install Telara can reach.
An API token or network path your Kubecost admin issued.

Vendor setup

Get the credential

1
Open Kubecost settings
In the Kubecost UI, open Settings → API (or Access / Tokens, depending on version).
2
Create a token
Create an API token. Copy it. Also copy the Kubecost frontend or API URL your cluster exposes.
3
Paste in Telara
Settings → Integrations → Kubecost. Enter the URL and token. If your install has no token auth, the form will ask for the reachable URL only — do not invent a key.

In Telara

Connect in Telara

API key

Kubecost base URL plus bearer/API token when the deployment requires authentication.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • Base Url
  • API key

Knowledge

What gets indexed

ResourceCoverage
Cost reportPartial — not every record the vendor holds is synced
Cost reportPartial — not every record the vendor holds is synced
Cost reportPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
Cost reportUp to 1 dayRemoved records disappear on the next full sync
Cost reportUp to 1 dayRemoved records disappear on the next full sync
Cost reportUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Cost report.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Kubecost must be reachable from Telara. A UI you can open on a VPN is not enough if Telara runs outside that VPN.
Allocation windows with no data are a Kubecost ETL issue, not always a bad token.