@kapa.ai in helm chart 2.0.19 how can i override temporal settings

In Helm Chart V2, you can override Temporal settings in your

values.yaml

file using the following approaches: Global Temporal Settings Use the

global.temporal

section for core Temporal configuration: [values.yaml reference] Temporal Pod-Level Overrides You can also configure the Temporal pod directly with extra environment variables, volumes, and volume mounts:

temporal:
  enabled: true
  replicaCount: 1

  # Additional env vars for temporal pod(s)
  extraEnv:
    - name: DYNAMIC_CONFIG_FILE_PATH
      value: config/dynamicconfig-override/development.yaml

  # Additional volumeMounts for temporal containers
  extraVolumeMounts:
    - name: my-temporal-config
      mountPath: "/etc/temporal/config/dynamicconfig-override/"

  # Additional volumes for temporal pods
  extraVolumes:
    - name: my-temporal-config
      configMap:
        name: my-temporal-configmap
        items:
          - key: development.yaml
            path: development.yaml

[Temporal pod override example] Known Limitation There is an open issue (as of 2.0.19) where

global.extraVolumes

and

global.extraVolumeMounts

are silently ignored for the

server

,

connector-builder-server

, and

temporal

deployment templates. If you need to mount volumes into the Temporal pod, use the pod-level

temporal.extraVolumes

and

temporal.extraVolumeMounts

instead of the global equivalents. [open issue] 👍 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

@kapa.ai how do i override those values: dynamicConfig: limit.maxIDWPSAllNamespaces: - value: 500 limit.maxBPS: - value: 500 history.persistenceMaxQPS: - value: 3000 history.persistenceNamespaceMaxQPS: - value: 3000 frontend.namespaceRPS: - value: 2400 frontend.maxNamespaceRPSPerInstance: - value: 2400

Based on the knowledge sources, here is how you can override Temporal dynamic config values in your Airbyte Helm deployment. Step 1: Create a ConfigMap with your dynamic config

apiVersion: v1
kind: ConfigMap
metadata:
  name: airbyte-platform-temporal-dynamicconfig-override
  namespace: airbyte  # Adjust namespace as needed
data:
  "development.yaml": |
    limit.maxIDWPSAllNamespaces:
      - value: 500
        constraints: {}
    limit.maxBPS:
      - value: 500
        constraints: {}
    history.persistenceMaxQPS:
      - value: 3000
        constraints: {}
    history.persistenceNamespaceMaxQPS:
      - value: 3000
        constraints: {}
    frontend.namespaceRPS:
      - value: 2400
        constraints: {}
    frontend.maxNamespaceRPSPerInstance:
      - value: 2400
        constraints: {}

Apply it with

kubectl apply -f <filename>.yaml

. Step 2: Override the Temporal pod config in your values.yaml

temporal:
  extraEnv:
    - name: DYNAMIC_CONFIG_FILE_PATH
      value: config/dynamicconfig-override/development.yaml

  extraVolumeMounts:
    - name: airbyte-temporal-dynamicconfig-override
      mountPath: "/etc/temporal/config/dynamicconfig-override/"

  extraVolumes:
    - name: airbyte-temporal-dynamicconfig-override
      configMap:
        name: airbyte-platform-temporal-dynamicconfig-override
        items:
          - key: development.yaml
            path: development.yaml

[Temporal dynamic config override] Step 3: Apply the Helm upgrade

helm upgrade airbyte-enterprise airbyte-v2/airbyte \
  --namespace airbyte-v2 \
  --values ./values.yaml \
  --version 2.0.19

[implementation guide] This approach mounts your custom dynamic config file into the Temporal pod and points Temporal to use it via the

DYNAMIC_CONFIG_FILE_PATH

environment variable. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.