@kapa.ai should I explicitly set RUN_DATABASE_MIGRATION_ON_STARTUP using helm chart v2 to ensure that bootloader runs migration during version bump?

The docs for Helm chart v2 map the legacy

RUN_DATABASE_MIGRATION_ON_STARTUP

env var to the Helm value

global.migrations.runAtStartup

(for both Community/Core and Enterprise).[Core chart v2; Enterprise chart v2] However, the provided sources do not state whether you must explicitly set it during a version bump, nor what the default is if you omit it. They only show the mapping and that this flag controls whether the bootloader runs migrations on startup.[Core chart v2] Given that limitation: • If you want to be certain migrations run during an upgrade, you should explicitly set

global.migrations.runAtStartup

in your

values.yaml

to the desired boolean (e.g.

true

), rather than relying on an undocumented default. • Be aware that in at least one non‑Helm setup, leaving

RUN_DATABASE_MIGRATION_ON_STARTUP

enabled caused issues for a specific upgrade, and the user fixed it by disabling/removing it; this is version‑ and schema‑specific and not documented as general guidance.[Airbyte wont start] Because the knowledge sources don’t document recommended upgrade practice for this flag with Helm v2, I cannot give a definitive “should/should not” beyond suggesting you set it explicitly according to your migration strategy. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai any guidelines on how to upgrade from 1.7.0 to 1.7.8 and then to 1.8.0 and 2.0.0 on selfhosted kubernetes setup without abctl?

The knowledge sources only give partial guidance for this exact path, but they do describe: • How to upgrade Airbyte on Kubernetes with Helm (no abctl). • How to move from Helm chart V1 → V2. • Examples for running 1.7.0 and 1.7.x on chart V2. Below is what’s documented; anything not stated in the docs I’ll call out as such. ------------------------- 1. General Helm-based upgrade flow (no abctl) For any in-place upgrade on Kubernetes with Helm (chart V1 or V2), the documented flow is: 1. Check what you’re currently running:

helm list -n <NAMESPACE>

This shows the current chart version. [Upgrading Airbyte 1.7; Upgrading Airbyte 1.8; Upgrading Airbyte 2.0] 2. Review release notes and available chart versions (on ArtifactHub). [Upgrading Airbyte 1.7] 3. Update your

values.yaml

only if needed (e.g., to use new features). [Upgrading Airbyte 1.7] 4. Run Helm upgrade: ~ bash # Helm chart V1 helm upgrade --install RELEASE-NAME airbyte/airbyte \ --values VALUES.YAML \ --version HELM-APP-VERSION

[[Upgrading Airbyte 1.7](https://docs.airbyte.com/platform/1.7/operator-guides/upgrading-airbyte); [Upgrading Airbyte](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)]

# Helm chart V2 helm upgrade airbyte airbyte-v2/airbyte \ --namespace NAMESPACE \ --values ./values.yaml \ --version 2.x.x 1. Confirm current chart/app version:

[[Upgrading Airbyte 2.0](https://docs.airbyte.com/platform/2.0/operator-guides/upgrading-airbyte); [Upgrading Airbyte](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)]
   ~~~


Upgrades require downtime; Airbyte will be temporarily unavailable. [<https://docs.airbyte.com/platform/2.0/operator-guides/upgrading-airbyte|Upgrading Airbyte 2.0>]

-------------------------

*2. From 1.7.0 → 1.7.8 (same major/minor)*

The docs don't mention 1.7.8 specifically, but they describe upgrading 1.7.x on Kubernetes with Helm using the generic flow above. [<https://docs.airbyte.com/platform/1.7/operator-guides/upgrading-airbyte|Upgrading Airbyte 1.7>]

So, staying on Helm chart V1:

helm list -n NAMESPACE 2. Find the Helm chart version that corresponds to app 1.7.8 on ArtifactHub (not in the provided snippets, so I can’t give the exact version). 3. Update

values.yaml

if needed. 4. Upgrade:

~~~ bash
   helm upgrade --install airbyte airbyte/airbyte \
     --namespace <NAMESPACE> \
     --values ./values.yaml \
     --version <HELM-CHART-VERSION-FOR-1.7.8>

[[Upgrading Airbyte 1.7](https://docs.airbyte.com/platform/1.7/operator-guides/upgrading-airbyte)] ~ The docs do not state that you must step through every patch (e.g., 1.7.0 → 1.7.8 vs directly to 1.8.0), so I can’t confirm whether intermediate steps are required. ------------------------- 3. Moving to Helm chart V2 (while on 1.7.x) For 1.7.0, the docs show how to deploy it using Helm chart V2 by pinning the image tag: [Chart V2 1.8 – Deploy Airbyte; Upgrading Airbyte 1.8] Example (fresh install into a V2 namespace):

helm install airbyte airbyte-v2/airbyte \
  --namespace airbyte-v2 \
  --values ./values.yaml \
  --version 2.0.3 \
  --set global.image.tag=1.7.0

For upgrading an existing 1.7.0 deployment in-place to chart V2, the docs show: [Chart V2 1.8 – Deploy Airbyte] 1. Backup the internal Postgres DB if you’re not using an external DB. [Chart V2 1.8 – How to upgrade] 2. Uninstall the old release but do not delete the namespace:

helm uninstall airbyte -n airbyte

3. Reinstall into the same namespace with chart V2:

helm install airbyte airbyte-v2/airbyte \
     --namespace airbyte \
     --values ./values.yaml \
     --version 2.0.3 \
     --set global.image.tag=1.7.0

Airbyte then continues in the same namespace, now on Helm chart V2. [Chart V2 1.8 – Deploy Airbyte] The same pattern exists in the 2.0 docs (without the

global.image.tag

override when app and chart versions match). [Chart V2 2.0 – Deploy Airbyte] ------------------------- 4. Upgrading to 1.8.0 and then 2.0.0 The docs do not give a step-by-step “1.7.0 → 1.7.8 → 1.8.0 → 2.0.0” sequence, but they do say: • Helm chart V2 can be used for Airbyte 1.6.0+ (Helm-managed). [Chart V2 Enterprise 1.8; Chart V2 Enterprise 2.0] • Once you’re on chart V2, you upgrade by changing the chart version (and, if needed, the image tag) and running

helm upgrade

. [Upgrading Airbyte 1.8; Upgrading Airbyte 2.0] A documented example for running 1.7.0 on chart V2 is: ~ bash helm upgrade airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.3 \ --set global.image.tag=1.7.0

[[Upgrading Airbyte 1.8](https://docs.airbyte.com/platform/1.8/operator-guides/upgrading-airbyte)]

For 2.0.0, the docs show chart V2 versions and how to install/upgrade, e.g.:

helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.18 # chart version, app version 2.0.0

[[Chart V2 2.0 – Deploy Airbyte](https://docs.airbyte.com/platform/2.0/deploying-airbyte/chart-v2-community#deploy-airbyte)]

And for upgrading an existing V2 deployment:

helm upgrade airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.x.x

[[Upgrading Airbyte 2.0](https://docs.airbyte.com/platform/2.0/operator-guides/upgrading-airbyte)]

The docs do not explicitly say whether you must go 1.7.x → 1.8.0 → 2.0.0 vs directly 1.7.x → 2.0.0; that guidance is not present in the provided sources.

---

### 5. Chart V1 → V2 upgrade prerequisites

For moving to chart V2 (for any supported version):

- Ensure you use an external DB and external bucket storage, **or** back up the internal Postgres DB. [[Chart V2 1.8 – How to upgrade](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#how-to-upgrade); [Chart V2 2.0 – How to upgrade](https://docs.airbyte.com/platform/2.0/deploying-airbyte/chart-v2-community#how-to-upgrade)]
- Add the V2 repo:

helm repo add airbyte-v2 https://airbytehq.github.io/charts helm repo update helm search repo airbyte-v2 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai we already on v2 helmchart, with app 1.7.0

Since you’re already on Helm chart V2 with app 1.7.0, the docs say you upgrade by changing the chart version (and, if needed, the image tag) and running

helm upgrade

. They don’t prescribe a specific sequence like 1.7.0 → 1.7.8 → 1.8.0 → 2.0.0, nor do they state that you must hit every intermediate version, so I can’t confirm that as a requirement. [Upgrading Airbyte 1.8; Upgrading Airbyte 2.0] What is documented for chart V2: 1. Identify compatible chart versions Use:

helm search repo airbyte-v2 --versions

This shows chart versions and their corresponding app versions, e.g. (excerpt): [Chart V2 2.0 – Deploy]

NAME                   CHART VERSION   APP VERSION
   airbyte-v2/airbyte     2.0.5           1.7.0
   airbyte-v2/airbyte     2.0.7           1.7.1
   ...
   airbyte-v2/airbyte     2.0.17          1.8.5
   airbyte-v2/airbyte     2.0.18          2.0.0

2. Upgrade within 1.7.x (if you want 1.7.8) The docs don’t list 1.7.8 explicitly, but the pattern is:

helm upgrade airbyte airbyte-v2/airbyte \
     --namespace <NAMESPACE> \
     --values ./values.yaml \
     --version <CHART_FOR_1.7.8> \
     --set global.image.tag=1.7.8   # only if chart appVersion differs

This follows the documented example for running 1.7.0 on chart V2 by pinning

global.image.tag

. [Chart V2 1.8 – Deploy; Upgrading Airbyte 1.8] 3. Upgrade to 1.8.0 on chart V2 Same pattern: pick a chart whose

APP VERSION

is 1.8.0 (or compatible) from

helm search repo airbyte-v2 --versions

, then:

helm upgrade airbyte airbyte-v2/airbyte \
     --namespace <NAMESPACE> \
     --values ./values.yaml \
     --version <CHART_FOR_1.8.0> \
     [--set global.image.tag=1.8.0]  # if needed

This is exactly the documented V2 Helm upgrade flow. [Upgrading Airbyte 1.8; Upgrading Airbyte] 4. Upgrade to 2.0.0 on chart V2 The docs show 2.0.0 running with chart

2.0.18

(APP VERSION 2.0.0): [Chart V2 2.0 – Deploy]

helm upgrade airbyte airbyte-v2/airbyte \
     --namespace <NAMESPACE> \
     --values ./values.yaml \
     --version 2.0.18

(No

global.image.tag

override needed when chart appVersion is already 2.0.0.) 5. General notes from the docs ◦ Upgrades require downtime; Airbyte will be temporarily unavailable. [Upgrading Airbyte 2.0] ◦ You normally only change

values.yaml

if you want new features or config changes. [Upgrading Airbyte 1.8] ◦ The docs don’t specify that you must go through 1.7.8 and 1.8.0 before 2.0.0, so I can’t state that as a requirement—only that each target version is upgraded via

helm upgrade

with the appropriate chart/app mapping. If you share the exact chart version you’re on now (e.g.

2.0.5

with app 1.7.0), you can apply this pattern directly by picking the next chart(s) from

helm search repo airbyte-v2 --versions

and upgrading in the order you prefer, using the commands above. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.