Enable Cloud Connectors

Cloud Connectors are off by default. Until you enable them, Central does not install the connector controller, the connector PostgreSQL store, or the OdigosCloudConnector CRD. Enabling the feature does not create per-account connectors. After the subsystem is running, add an AWS or GCP connector from the Central UI.

Cloud Connectors require the same Odigos Enterprise on-prem token (or install secret) as the rest of the Central installation.

What gets installed

When cloudConnectors.enabled is true and the Central install secret exists, the chart installs:

The OdigosCloudConnector CRD
The connector-runtime controller
Bundled PostgreSQL (odigos-connector-postgres) and a PVC when persistence is enabled

A StorageClass must be defined for the Postgres PVC. Bundled Postgres uses a PVC for connector state management; without a usable StorageClass the PVC cannot bind. Set cloudConnectors.postgres.persistence.storageClassName explicitly, or leave it empty to use the cluster default.

Enable Cloud Connectors

CLI
Helm

At install time:

odigos pro central install \
  --set onPremToken=<token> \
  --set cloudConnectors.enabled=true \
  --set cloudConnectors.postgres.password=<strong-password> \
  --set cloudConnectors.postgres.persistence.enabled=true \
  --set cloudConnectors.postgres.persistence.size=20Gi \
  --set cloudConnectors.postgres.persistence.storageClassName=

On an existing Central installation:

odigos pro central upgrade \
  --set cloudConnectors.enabled=true \
  --set cloudConnectors.postgres.password=<strong-password> \
  --set cloudConnectors.postgres.persistence.enabled=true \
  --set cloudConnectors.postgres.persistence.size=20Gi \
  --set cloudConnectors.postgres.persistence.storageClassName=

Leave storageClassName empty to use the cluster default, or set it to a class your cluster requires (e.g. gp3).

Enable with --set:

helm upgrade --install odigos-central odigos/odigos-central \
  --namespace odigos-central \
  --reuse-values \
  --set cloudConnectors.enabled=true \
  --set cloudConnectors.postgres.password=<strong-password> \
  --set cloudConnectors.postgres.persistence.enabled=true \
  --set cloudConnectors.postgres.persistence.size=20Gi \
  --set cloudConnectors.postgres.persistence.storageClassName=

Or in values.yaml:

cloudConnectors:
  enabled: true
  postgres:
    password: "<strong-password>"
    persistence:
      enabled: true
      size: 20Gi
      storageClassName: "" # set if your cluster requires an explicit class

Then apply:

helm upgrade --install odigos-central odigos/odigos-central \
  --namespace odigos-central \
  --create-namespace \
  -f values.yaml

PostgreSQL configuration

Cloud Connectors use a bundled PostgreSQL instance under cloudConnectors.postgres. Configure these values when you enable the feature:

string

default:"odigos"

Database password. Change this for non-development installs.

string

default:"odigos"

Database username.

string

default:"odigos_central"

Database name.

boolean

default:"true"

Persist connector state on a PVC.

string

default:"20Gi"

PVC size. Your cluster must provide storage.

string

default:""

Storage class. Empty uses the cluster default.

Advanced Postgres settings

Value	Default	Description
`postgres.persistence.accessModes`	`[ReadWriteOnce]`	PVC access modes
`postgres.resources`	chart defaults	CPU and memory requests/limits for the Postgres pod
`postgres.image`	chart default	Leave at the chart default unless Odigos support or engineering asks you to override it

Do not set a custom Postgres image on your own. Use the image shipped with the chart unless Odigos support or engineering directs otherwise.

Optional provider image overrides

Provider connector images (cloudConnectors.aws.image, cloudConnectors.gcp.image) default to the versions shipped with the chart.

Override these only when Odigos support or engineering asks you to. Custom images can break discovery, instrumentation, or schema compatibility.

cloudConnectors:
  enabled: true
  aws:
    image: "" # empty = chart default; set only if directed by Odigos
  gcp:
    image: "" # empty = chart default; set only if directed by Odigos

Verify

After enablement, confirm the subsystem is running in the Central namespace (default odigos-central):

kubectl get pods -n odigos-central -l 'app in (connector-runtime,odigos-connector-postgres)'

You should see connector-runtime and odigos-connector-postgres in a Running state.

Once both pods are Running, you are ready to add a cloud provider connector.

Next steps

Add AWS connector

Connect an AWS account.

Add GCP connector

Connect a Google Cloud project.

Instrument workloads

Create Sources after a connector is online.

​What gets installed

​Enable Cloud Connectors

​PostgreSQL configuration

​Verify

​Next steps

Add AWS connector

Add GCP connector

Instrument workloads

What gets installed

Enable Cloud Connectors

PostgreSQL configuration

Verify

Next steps