@kapa.ai Hello, I'm using the following

env

variables in airbytes helm chart v.1.9.1

temporal:
  extraEnv:
    - name: SQL_TLS
      value: "true"
    - name: SQL_TLS_DISABLE_HOST_VERIFICATION
      value: "true"
    - name: SQL_TLS_ENABLED
      value: "true"
    - name: SQL_HOST_VERIFICATION
      value: "false"
    - name: POSTGRES_TLS_ENABLED
      value: "true"
    - name: POSTGRES_TLS_DISABLE_HOST_VERIFICATION
      value: "true"
    - name: TEMPORAL_HISTORY_RETENTION_IN_DAYS
      value: "30"
    - name: DBNAME
      value: "data_temporal"
    - name: VISIBILITY_DBNAME
      value: "data_temporalvisibility"
    - name: SKIP_DB_CREATE
      value: "true"

I'm upgrading to the helm chart v2.1.0 . Do these values still work? If not how do i migrate them to the new helm chart? Also can yo uplease provide a reference in code to these variables

Migrating Temporal extraEnv Variables to Helm Chart V2 Looking at your variables, here's what the documentation says about migrating to Helm chart V2: What Has a Direct V2 Equivalent Only one of your variables has a documented direct equivalent in Helm chart V2: According to the migration docs,

TEMPORAL_HISTORY_RETENTION_IN_DAYS

does not have a dedicated V2 interface — it should still be passed via

extraEnvs

. [chart V2 upgrade] What the Docs Don't Cover The knowledge sources do not contain information about the following variables you're using: •

SQL_TLS

•

SQL_TLS_DISABLE_HOST_VERIFICATION

•

SQL_TLS_ENABLED

•

SQL_HOST_VERIFICATION

•

POSTGRES_TLS_ENABLED

•

POSTGRES_TLS_DISABLE_HOST_VERIFICATION

•

DBNAME

•

VISIBILITY_DBNAME

•

SKIP_DB_CREATE

These appear to be Temporal-specific database configuration variables. The migration documentation does not explicitly address these, so I cannot confirm whether they have dedicated V2 equivalents or must remain as

extraEnvs

. How to Pass Variables Without a Direct V2 Equivalent For variables without a dedicated V2 interface, you should use

extraEnvs

under the relevant service section. Based on the V2 syntax, your

temporal

section would look like:

temporal:   extraEnvs:     - name: SQL_TLS       value: "true"     - name: SQL_TLS_DISABLE_HOST_VERIFICATION       value: "true"     - name: SQL_TLS_ENABLED       value: "true"     - name: SQL_HOST_VERIFICATION       value: "false"     - name: POSTGRES_TLS_ENABLED       value: "true"     - name: POSTGRES_TLS_DISABLE_HOST_VERIFICATION       value: "true"     - name: TEMPORAL_HISTORY_RETENTION_IN_DAYS       value: "30"     - name: DBNAME       value: "data_temporal"     - name: VISIBILITY_DBNAME       value: "data_temporalvisibility"     - name: SKIP_DB_CREATE       value: "true"

> Note: The key change is

extraEnv

→

extraEnvs

(plural). [chart V2 upgrade] Important Caveat The documentation does not explicitly confirm that all these Temporal TLS/DB variables are still respected in V2, or whether some may now have dedicated chart-level fields. I'd recommend checking the Airbyte Helm chart V2 values reference directly for the

temporal

section to verify if any of these have native V2 equivalents. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

The key is actually

extraEnv

, it is not

extraEnvs