The behavior you describe (getting 1.6.0) almost always comes from Helm still using the old V1 chart repo instead of the new V2 repo, even if

helm search repo airbyte-v2

looks correct. From the docs and GitHub issues, to install Airbyte 2.x via Helm chart V2 you must: 1. Ensure the V2 repo URL is correct The V2 chart is served from the

airbyte-v2

repo (not the legacy

airbyte

/

helm-charts

one). The docs and issues show examples assuming

airbyte-v2

is already added and indexed. [[Core chart V2](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte); [Enterprise chart V2](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise#deploy-airbyte)] Please explicitly reset it:

bash    helm repo remove airbyte || true    helm repo remove airbyte-v2 || true     # Re‑add only the V2 repo    helm repo add airbyte-v2 <https://airbytehq.github.io/charts>    helm repo update     helm search repo airbyte-v2 --versions

Verify that the row for

2.0.19

indeed shows

APP VERSION 2.0.1

, as you posted. 2. Use the V2 chart with

--version

set to the chart version The docs show that to deploy 2.0.0 you use chart `2.0.18`; in your case, you want

2.0.19

(APP VERSION 2.0.1). The install should look like:

bash    helm install airbyte airbyte-v2/airbyte \      --namespace airbyte-v2 \      --values ./helm/v2/values.yaml \      --version 2.0.19

This pattern is identical to the examples with

2.0.18

in the docs. [[Core chart V2](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte); [Enterprise chart V2](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise#deploy-airbyte)] 3. Double‑check what’s actually running If you still see 1.6.0, it may be from an existing deployment in the same namespace created earlier with the V1 chart. The upgrade guide explicitly tells you to

helm uninstall airbyte

before reinstalling with the V2 chart, while keeping the namespace. [[Chart V2 upgrade](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte)] In that case:

bash    # If you’re upgrading, first uninstall the old release in that namespace    helm uninstall airbyte -n airbyte-v2   # or your namespace     # Then reinstall using the V2 chart    helm install airbyte airbyte-v2/airbyte \      --namespace airbyte-v2 \      --values ./helm/v2/values.yaml \      --version 2.0.19

If after: - cleaning/removing old repos, - re‑adding

airbyte-v2

with the documented URL, - uninstalling any previous

airbyte

release in that namespace, you still see 1.6.0, then based on the available docs/issues I don’t have further specific causes; the knowledge sources don’t document another scenario that would produce that mismatch.

To use reverse ETL (Data Activation) you need two things: 1. An Airbyte version that supports it Data activation is available starting with Airbyte 1.8+ and is now part of the core “Moving data” capabilities. [[Data activation intro](https://docs.airbyte.com/platform/move-data/elt-data-activation); [1.8 release notes](https://docs.airbyte.com/release_notes/v-1.8)] You’re on 2.0.1, which is new enough. 2. Supported destinations and connection setup In early access, reverse ETL is supported for HubSpot and Customer.io (plus an Enterprise Salesforce destination). [[1.8 release notes](https://docs.airbyte.com/release_notes/v-1.8); [Early‑access discussion](https://github.com/airbytehq/airbyte/discussions/63711)] The high‑level flow is: - Source: your warehouse (e.g. Snowflake, BigQuery, Redshift) configured as a source. - Destination: one of the reverse‑ETL‑capable connectors (HubSpot, Customer.io, etc.) configured as a destination. [[Data activation intro](https://docs.airbyte.com/platform/move-data/elt-data-activation)] - Connection: create a connection from the warehouse source to that destination and configure field mappings and sync mode (insert/update/upsert/soft delete). [[Data activation intro](https://docs.airbyte.com/platform/move-data/elt-data-activation); [Get started](https://docs.airbyte.com/platform/move-data/elt-data-activation#get-started)] If you “don’t see new destinations”: - The docs list HubSpot and Customer.io as the initial data‑activation destinations, plus an Enterprise‑only Salesforce destination. [[1.8 release notes](https://docs.airbyte.com/release_notes/v-1.8)] - The knowledge sources don’t describe any extra UI flag or feature toggle you might need to enable; they assume these destinations appear in the catalog for supported editions. If they’re missing from your destination list, the docs don’t give a specific troubleshooting path for that case. Next steps based on docs: - Verify you’re looking under Destinations → New Destination and search for “HubSpot” or “Customer.io”. [[Add destination](https://docs.airbyte.com/platform/using-airbyte/getting-started/add-a-destination)] - Follow the “Get started” guide for Data Activation once you see them: set up a warehouse source, one of those destinations, then a connection with mappings. [[Get started](https://docs.airbyte.com/platform/move-data/elt-data-activation#get-started)] If, after that, those destinations still don’t appear, the available documentation does not explain why; it suggests filling out the early‑access feedback form or engaging with the team, but doesn’t provide additional configuration steps. [[1.8 data activation](https://docs.airbyte.com/platform/1.8/move-data/elt-data-activation); [Early‑access discussion](https://github.com/airbytehq/airbyte/discussions/63711)]