Skip to main content
Version Next

Integrations — OpenMetadata

Integration overview​

The tdp-openmetadata chart can run a post-install/upgrade Job that registers external services in OpenMetadata when datasourcesIntegration.enabled=true.

Overview​

  1. Deploy OpenMetadata.
  2. The Job waits for OpenMetadata to be ready, authenticates against the API, and registers the enabled services.

Enabling the Job​

datasourcesIntegration:
  enabled: true

Access to the OpenMetadata API is configured under datasourcesIntegration.openmetadata.*. If datasourcesIntegration.openmetadata.auth.passwordSecret.enabled=true, provide the Secret name and password key in your values file.

Per-service configuration​

Each integration has an enabled flag and a connection block under datasourcesIntegration.*.

Example (Trino + ClickHouse)​

datasourcesIntegration:
  enabled: true
  openmetadata:
    apiEndpoint: "http://<openmetadata-service>.<namespace>.svc.cluster.local:8585/api"
    auth:
      provider: "basic"
      username: "admin@open-metadata.org"
      passwordSecret:
        enabled: true
        name: "<openmetadata-admin-secret>"
        key: "<password-key>"

  trino:
    enabled: true
    connection:
      host: "<trino-service>.<namespace>.svc.cluster.local"
      port: 8080
      username: "<username>"
      scheme: "http"

  clickhouse:
    enabled: true
    connection:
      host: "<clickhouse-service>.<namespace>.svc.cluster.local"
      port: 8123
      username: "<username>"
      passwordSecret:
        name: "<clickhouse-secret>"
        key: "password"
      scheme: "http"

Airflow, Superset, and Kafka​

Airflow, Superset, and Kafka are supported types by the Job (Pipeline, Dashboard, Messaging): enable the corresponding block and fill in connection and credentials in the values file (see helm show values).

Typical installation with extra values (generic example):

Terminal input
helm upgrade --install <release> \
  oci://registry.tecnisys.com.br/tdp/charts/tdp-openmetadata \
  -n <namespace> \
  -f <base-file>.yaml \
  -f <integrations-file>.yaml

Use values files from your Helm package or a single -f with all required content.

Verification​

After the Job completes, the services should appear in the OpenMetadata UI under Settings → Services.

Troubleshooting​

Terminal input
kubectl -n <namespace> get jobs
kubectl -n <namespace> logs job/<release>-register-datasources