Hi @kapa.ai How to reduce the max number of attempts on Airbyte Open Source version 2.0.1 deployed via Helm/Kubernetes ?

Reducing Max Sync Attempts in Airbyte OSS (Helm/Kubernetes) On self-managed Airbyte, the retry/attempt limits are controlled by environment variables. [Retry Rules] Relevant Environment Variables [Jobs Config] How to Set These in Helm (Chart V2) For Helm chart V2, these variables should be set via

extraEnvs

on the relevant component. [Helm Chart V2 Upgrade] In your `values.yaml`:

worker:
  extraEnv:
    - name: SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_SUCCESSIVE
      value: "3"
    - name: SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_TOTAL
      value: "5"
    - name: SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_TOTAL
      value: "10"

> Note: There is a known GitHub issue reporting that env var overrides via Helm (e.g.,

extraEnv

,

global.env_vars

) may not always be respected in certain Helm chart versions around 1.5.x. [GitHub Issue] If your values are not being picked up, you may need to verify the rendered ConfigMap after deployment to confirm the values are applied correctly. Alternative: Global env_vars You can also try setting them under `global.env_vars`:

global:
  env_vars:
    SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_SUCCESSIVE: "3"
    SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_TOTAL: "5"
    SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_TOTAL: "10"

After applying, verify the values are reflected in the

airbyte-env

ConfigMap in your namespace. 👍 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