@kapa.ai I’m planning to upgrade Airbyte to

2.1.0

, but I noticed that Helm chart V1 is no longer supported starting with this release. Helm chart V2 is now the only supported chart, and migration to V2 is required to continue receiving updates. Current setup: • Helm chart version:

1.9.1

• Airbyte runtime/app version:

2.0.1

Is the upgrade from this setup to Airbyte

2.1.0

expected to be straightforward, or are there any migration steps, breaking changes, or cautions we should be aware of before proceeding?

Thinking completed Upgrading from Airbyte

2.0.1

on Helm chart

1.9.1

(V1) to Airbyte

2.1.0

requires migrating to Helm chart V2, as Helm chart V1 is completely unsupported starting in Airbyte 2.1.0 [Airbyte 2.1 Release Notes]. While the upgrade path is supported, it is *not a simple in-place chart bump*; there are essential migration steps, breaking configuration changes, and version cautions you should be aware of. Important Cautions for Version 2.1.0 • Experimental Release Status: The release notes explicitly flag Airbyte

2.1.0

as experimental, noting that not every feature and Helm chart configuration has been fully tested. If stability is your primary concern, consider waiting for a subsequent patch release [Airbyte 2.1 Release Notes]. • Self-Managed Enterprise Warning: If you are using Self-Managed Enterprise, the release notes warn not to upgrade and to contact Airbyte about switching to Cloud [Airbyte 2.1 Release Notes]. Key Migration Steps Because you are transitioning from Helm chart V1 to V2, follow the official migration process [Upgrade to Helm chart V2]: 1. Database & Storage Requirements: ◦ Ensure Airbyte is configured with an external database and bucket storage. ◦ If using the internal PostgreSQL database (

airbyte-db-0

), you must create a manual backup (via

pg_dump

) before doing anything else to prevent loss of connections and sync states [Upgrade to Helm chart V2]. 1. Namespace Deployment Strategy: ◦ If using an external database: Airbyte recommends performing a fresh install into a new namespace (e.g.,

airbyte-v2

) rather than an in-place upgrade, which makes troubleshooting custom values significantly easier [Upgrade to Helm chart V2]. ◦ If using the internal database: You will reinstall Airbyte into your existing namespace to preserve the persistent volume [Upgrade to Helm chart V2]. 1. *Add the New Helm Repository:*helm repo add airbyte-v2 https://airbytehq.github.io/charts helm repo update[Upgrade to Helm chart V2; GitHub Issue #68134] ◦ Chart V2 is hosted in a different repository URL (

/charts

instead of

/helm-charts

): Breaking Changes & Configuration Updates When migrating your

values.yaml

from V1 to V2, you will need to update several key structures and account for 2.1 changes [Update your values.yaml file; Airbyte 2.1 Release Notes]: 1. Key Naming and Casing Changes (V1 → V2) • Kebab-case to camelCase: Hyphenated component keys must be converted (e.g.,

workload-launcher

becomes

workloadLauncher

,

airbyte-bootloader

becomes

airbyteBootloader

) [Update your values.yaml file]. • Renamed Keys: ◦

orchestrator

→

containerOrchestrator

◦

global.database.database

→

global.database.name

◦ Bucket storage variables move from individual env vars (like

S3_LOG_BUCKET

,

STORAGE_BUCKET_STATE

) to

global.storage.bucket.*

[Update your values.yaml file]. 2. Environment Variables to Dedicated Fields Many settings previously defined via

extraEnv

now have dedicated top-level or structured fields. For example: • Worker concurrency:

worker.extraEnvs[MAX_SYNC_WORKERS]

is now

worker.maxSyncWorkers

[Update your values.yaml file]. • Job node selectors:

workload-launcher.extraEnvs[JOB_KUBE_NODE_SELECTORS]

is now configured under

global.jobs.kube.nodeSelector

[Update your values.yaml file]. 3. Airbyte 2.1-Specific Breaking Changes • Authentication enabled by default: New deployments require authentication out-of-the-box. If you require unauthenticated access, you must explicitly disable it in your values [Airbyte 2.1 Release Notes]. • Management endpoints moved to Port 8085: Micronaut health and metric endpoints moved from the primary application port to port

8085

. If you maintain custom external probes, health checks, or Prometheus scrapes, update their target port [Airbyte 2.1 Release Notes]. •

AIRBYTE_ROLE

removed: The

AIRBYTE_ROLE

environment variable has been completely removed. Clean this up if it appears in your custom configs or scripts [Airbyte 2.1 Release Notes]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.