Skip to main content
Version Next

Integrations — Airflow

Integration overview​

The tdp-airflow chart supports integration with an external PostgreSQL instance (Airflow metadata) and the creation of an S3 connection Secret via TDPConfigurations.s3Connection.

Integration with external PostgreSQL​

Prerequisite: a tdp-postgresql instance or release accessible within the cluster, with a known internal DNS host.

Use an additional values file (e.g. values-external-db.yaml) with placeholders:

tdp-airflow:
  postgresql:
    enabled: false

  data:
    metadataSecretName: "<release>-airflow-database"
    metadataConnection:
      user: airflow
      pass: ""
      protocol: postgresql
      host: "<postgresql-host>.<namespace>.svc.cluster.local"
      port: 5432
      db: airflow
      sslmode: disable

TDPConfigurations:
  externalDatabase:
    enabled: true
    recreate: false
    externalSecret:
      releaseName: "<tdp-postgresql-release>"
      area: "<area>"
Terminal input
helm upgrade --install <release> \
  oci://registry.tecnisys.com.br/tdp/charts/tdp-airflow \
  -n <namespace> \
  -f values.yaml \
  -f values-external-db.yaml

The area field is used by TDP helpers to compose the external database context.

Integration with S3 / compatible storage​

Enabling TDPConfigurations.s3Connection creates a Secret with connection parameters for TDP integrations (S3-compatible endpoint):

TDPConfigurations:
  s3Connection:
    enabled: true
    secretName: "<s3-connection-secret>"
    name: "<connection-name>"
    type: "aws"
    accessKey: "<access-key>"
    secretKey: "<secret-key>"
    uri: "https://<s3-endpoint>"
Terminal input
helm upgrade --install <release> \
  oci://registry.tecnisys.com.br/tdp/charts/tdp-airflow \
  -n <namespace> \
  -f values.yaml \
  -f values-s3.yaml
Credentials

Avoid committing accessKey and secretKey to a repository. Prefer targeted --set flags, cluster-level secret management, or references via tdp-airflow.extraEnv, in accordance with your environment's policy.