Dmytro Shamenko
03/03/2026, 11:13 AMkapa.ai
03/03/2026, 11:13 AM2.0.3), you would run:
helm install airbyte airbyte-v2/airbyte \
--namespace airbyte-v2 \ # Target Kubernetes namespace
--values ./values.yaml \ # Custom configuration values
--version 2.0.3 \ # Helm chart version to use
--set global.image.tag=1.7.0 # Airbyte version to use
[chart v2 community 1.8]
The documentation explicitly notes: "Since using this chart version is optional, the Helm chart and Airbyte have different, but compatible, versions." [chart v2 community 1.8]
A few things to keep in mind:
⢠Helm chart V2 requires Airbyte version 1.6.0 or later ā so 1.7.x qualifies. [chart v2 enterprise]
⢠Make sure to use the airbyte-v2 repo (not the legacy airbyte repo) when deploying with Helm chart V2:
helm repo add airbyte-v2 https://airbytehq.github.io/charts
helm repo update
[chart v2 enterprise 2.0] š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Dmytro Shamenko
03/03/2026, 11:15 AMkapa.ai
03/03/2026, 11:15 AMvalues.yaml reference does include tolerations fields for various components (e.g., webapp, keycloak, keycloak-setup, workload-api-server, workload-launcher), which are the standard Kubernetes mechanism used alongside taints: [values reference]
# -- Tolerations for webapp pod assignment, see https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []
However, I cannot confirm from the available knowledge sources whether there were specific taint-related bugs in past versions or whether they are fully resolved in the 2.0 chart. For a definitive answer on this, I'd recommend:
1. Checking the Airbyte GitHub issues for any taint-related bug reports.
2. Reaching out to the Airbyte community on their Slack or GitHub Discussions. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.