I'm trying to deploy Airbyte using Helm and I want to deploy the Temporal chart as a separate release so that I can provide a custom DB configuration for it that is slightly different than the global one (I want to use PGBouncer for the global one). It seems like the Temporal chart is refering to the

airbyte-secrets

(https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte-temporal/templates/deployment.yaml#L70)

Secret

that is created by the main

airbyte

chart (its not created by

airbyte/temporal

) and the way it is written, it seems like it is expecting them to use the same

.Release.Name

which wouldn't be possible. I cannot have 2 separate releases with same name. Is this a bug in the Temporal helm chart or am I missing something? It feels like

{{ .Release.Name }}-airbyte-secrets

will never evaluate to the release where that secret is created if the charts are deployed separately in this manner.

Based on the information provided in the extracts, it seems like you're correct in your understanding. If you're deploying the Temporal chart as a separate release, it might not be able to access the

airbyte-secrets

created by the main

airbyte

chart if they don't share the same

.Release.Name

. In a [previous Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1666723590268439), a user was trying to run Temporal externally in Kubernetes and wanted to override the default DB creation process. The user was advised to override it using the

global.database

and

externalDB

block, and it was also suggested that

env_vars

or

extraEnv

blocks could be used to provide environment variables specifically for Temporal. However, the conversation also suggested that if these methods don't work, modifying the shell script might be required. This might be the case for your situation as well. Unfortunately, the extracts don't provide a definitive solution to your problem. It might be a good idea to reach out to the Airbyte community for further assistance.

I was able to resolve this with the following steps: • As part of the

airbyte-temporal

chart, change

deploymentMode

away from

oss

to prevent default environment variables to be added. • Added

extraEnv

for

AUTO_SETUP

,

DB

,

DB_PORT

,

POSTGRES_USER

,

POSTGRES_PWD

,

POSTGRES_SEEDS

,

DYNAMIC_CONFIG_FILE_PATH

• Updated the

airbyte

chart to have

TEMPORAL_HOST

env variable pointing to the new

airbyte-temporal

service created. This env var must contain port.