Skip to main content
Use this page to operate connectors after they are online — health, immutable fields, and safe removal.

Connector status

The connectors list and detail views show installation and runtime health. The connector phase is one of:
Degraded usually means:
  • A discovery cycle failed (missing permissions, cloud API errors, or other detector failures)
  • The runtime stopped refreshing its heartbeat (for example the pod is wedged or lost its Postgres connection), so the last healthy status went stale
Auth that has not succeeded yet, or discovery that has not completed a successful cycle yet, typically stays in Starting rather than Degraded.Error usually means:
  • The connector image could not be resolved for the provider
  • spec.provider was changed after the connector was created (provider is immutable)
Schema version mismatches fail connector startup (the pod does not stay healthy), which typically shows as Starting or, if heartbeats stop updating, Degraded — not a dedicated schema-mismatch phase.Fix credentials or IAM, confirm Cloud Connectors are enabled, and check connector-runtime / connector pods in the Central namespace.

What you can change

  • You can update display name, credentials Secret contents, discovery interval, and capabilities (which types to discover/instrument), depending on what the UI exposes for your version.
  • provider is immutable after the connector is created. To switch providers (for example from AWS to another cloud), create a new connector.

Delete a connector

Deleting a connector removes the connector runtime from the Central cluster. What happens to cloud-side instrumentation depends on the deletion policy annotation on the OdigosCloudConnector resource:
Deletes the connector from Central (the connector pod and related resources in the Central cluster). It does not uninstrument cloud workloads.Any Odigos instrumentation already applied in the cloud account stays in place (for example Lambda layers or Cloud Run agent injection). To remove that instrumentation, uninstrument Sources while the connector is still online, or change those resources outside Odigos after delete.
Creating a connector from the Central UI typically leaves the annotation unset, which means retain.

Sources on delete

When you delete a connector, Sources and discovery data for that account boundary are no longer managed through that connector.
Prefer disabling or deleting Sources first if you want a controlled rollback while the connector is still running, especially under the default retain policy.

Instrument workloads

Create and disable Sources while the connector is online.

Cloud Connectors overview

Back to concepts and supported providers.