Saltar para o conteúdo principal
Versão Next

Integrações — CloudBeaver

Visão geral das integrações

O chart tdp-cloudbeaver permite habilitar datasources (ClickHouse, Trino), PostgreSQL externo para metadados e variáveis de ambiente para armazenamento S3-compatível.

ClickHouse

tdp-cloudbeaver:
dataSources:
enabled: true
enabledClickhouse: true
clickhouseHost: "<clickhouse-service>.<namespace>.svc.cluster.local"
clickhousePort: 8123
database: "default"
user: "tdpuser"
passwordSecret:
name: "<clickhouse-password-secret>"
key: "password"
Terminal input
kubectl create secret generic <clickhouse-password-secret> \
--from-literal=password='<password>' \
-n <namespace>

Trino

tdp-cloudbeaver:
dataSources:
enabled: true
enabledTrino: true
nameConnector: "Trino TDP"
trinoHost: "<trino-service>.<namespace>.svc.cluster.local"
trinoPort: 8080
database: "default"
user: "admin"

PostgreSQL (metadados)

tdp-cloudbeaver:
database:
enabled: true
type: "postgresql"
host: "<postgresql-service>.<namespace>.svc.cluster.local"
port: "5432"
databaseName: "cloudbeaver_db"
schema: "public"
user: "cloudbeaver_user"
driver: "postgres-jdbc"
passwordSecret:
name: "cloudbeaver-db-secret"
key: "password"
postgresSecret:
name: "<postgresql-admin-secret-name>"
key: "postgres-password"

S3 / MinIO

Terminal input
kubectl create secret generic cloudbeaver-s3-credentials \
--from-literal=access-key='<access-key>' \
--from-literal=secret-key='<secret-key>' \
-n <namespace>
tdp-cloudbeaver:
extraEnvVars:
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: cloudbeaver-s3-credentials
key: access-key
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: cloudbeaver-s3-credentials
key: secret-key
- name: S3_ENDPOINT
value: "https://<s3-endpoint>"
- name: S3_BUCKET
value: "<bucket-name>"

Combinando arquivos de valores

Terminal input
helm upgrade --install <release> \
oci://registry.tecnisys.com.br/tdp/charts/tdp-cloudbeaver \
-n <namespace> \
-f meu-values.yaml \
-f values-integracao.yaml