Integrations — Trino
Integration overview
The tdp-trino chart integrates data sources by defining catalogs under trino.catalogs. There is no fixed list of mandatory values-*-connector.yaml files: each environment combines connector properties in its own values file (or in additional Helm layers).
Configuration pattern
helm upgrade --install <release> \
oci://registry.tecnisys.com.br/tdp/charts/tdp-trino \
-n <namespace> \
-f my-values.yaml
Add or modify blocks under trino.catalogs according to the Trino documentation for each connector.
Catalog examples (placeholders)
Adjust hosts, ports, and credentials to your cluster. Keys are always under trino (do not use an alternative prefix).
JDBC (e.g. PostgreSQL)
trino:
catalogs:
analytics: |
connector.name=postgresql
connection-url=jdbc:postgresql://<db-service>.<namespace>.svc.cluster.local:5432/<database>
connection-user=<user>
connection-password=<password>
Hive / Iceberg with metastore and S3-compatible storage
Illustrative values — check the connector documentation for exact property names in your version of Trino:
trino:
catalogs:
hive: |
connector.name=hive
hive.metastore.uri=thrift://<hive-metastore-service>.<namespace>.svc.cluster.local:9083
# Storage properties (S3, etc.) as per Trino documentation and your provider
iceberg: |
connector.name=iceberg
iceberg.catalog.type=hive_metastore
hive.metastore.uri=thrift://<hive-metastore-service>.<namespace>.svc.cluster.local:9083
ClickHouse (JDBC)
trino:
catalogs:
clickhouse: |
connector.name=clickhouse
connection-url=jdbc:clickhouse://<clickhouse-service>.<namespace>.svc.cluster.local:8123/<database>
connection-user=<user>
connection-password=<password>
Advanced access control (e.g. Ranger) depends on what your package exposes under trino.accessControl; if not covered in this documentation, follow the official Trino documentation and validate with helm show values for your version.
For LDAP, TLS, and Ingress, see Trino Configuration, Ingress — Trino, and Security — Trino.