Integrations / Argo CD

Argo CD

Argo CD GitOps deployment platform for applications, sync status, projects, clusters, repositories, and release drift.

Bearer token

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

An Argo CD instance Telara can reach on the network.

An account that can create an API token (or a local user whose JWT you mint).

Vendor setup

Get the credential

Open your Argo CD UI (the host you will enter as the instance URL, without https).

Create an account token

Open User Info → Tokens (or Settings → Accounts → Tokens). Generate a token for a least-privilege account. Copy it once.

Paste in Telara

Settings → Integrations → Argo CD. Enter the Argo CD host without scheme, then paste the token.

In Telara

Connect in Telara

Bearer token

Argo CD API JWT generated for a least-privilege account. Store base_url as the tenant Argo CD host without scheme.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for

Base Url
API token

Knowledge

What gets indexed

Resource	Coverage
Application	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Application	Up to 1 day	Removed 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: Application.

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

The host must be the API the UI talks to, not a separate SSO login page Telara cannot reach.

A token from an account that cannot list applications connects and then looks empty.