Ashis Parajuli
06/25/2025, 10:28 PMIan Alton
07/07/2025, 9:27 PMClaudio Paladini
08/18/2025, 8:08 AMJulien Ruey
08/19/2025, 2:32 PMjsonb type ? It's actually parsed and loaded into S3 as string type. We have more and more use case of providers and tables from our internal backend db using this type of field. We 're apparently not the only ones facing this challenge (https://airbytehq.slack.com/archives/C021JANJ6TY/p1713996557175259).
Bests,Rachel Ambler
08/25/2025, 4:15 PMINFO Using Kubernetes provider:
Provider: kind
Kubeconfig: /root/.airbyte/abctl/abctl.kubeconfig
Context: kind-airbyte-abctl
SUCCESS Found Docker installation: version 28.3.3
SUCCESS Existing cluster 'airbyte-abctl' found
SUCCESS Cluster 'airbyte-abctl' validation complete
WARNING Found MinIO physical volume. Consider migrating it to local storage (see project docs)
WARNING Psql 13 detected. Consider upgrading to 17
INFO Pulling image airbyte/connector-builder-server:1.8.1
INFO Pulling image airbyte/cron:1.8.1
INFO Pulling image airbyte/server:1.8.1
INFO Pulling image airbyte/worker:1.8.1
INFO Pulling image airbyte/workload-api-server:1.8.1
INFO Pulling image airbyte/workload-launcher:1.8.1
INFO Pulling image temporalio/auto-setup:1.27.2
INFO Namespace 'airbyte-abctl' already exists
INFO Persistent volume 'airbyte-minio-pv' already exists
INFO Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' already exists
INFO Persistent volume 'airbyte-volume-db' already exists
INFO Persistent volume claim 'airbyte-volume-db-airbyte-db-0' already exists
INFO Starting Helm Chart installation of 'airbyte/airbyte' (version: 2.0.10)
ERROR Failed to install airbyte/airbyte Helm Chart
ERROR Unable to install Airbyte locally
ERROR unable to install airbyte chart: unable to install helm: cannot patch "airbyte-abctl-connector-builder-server" with kind Deployment: Deployment.apps "airbyte-abctl-connector-builder-server" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"airbyte":"connector-builder-server", "<http://app.kubernetes.io/instance|app.kubernetes.io/instance>":"airbyte-abctl", "<http://app.kubernetes.io/name|app.kubernetes.io/name>":"connector-builder-server"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable && cannot patch "airbyte-abctl-cron" with kind Deployment: Deployment.apps "airbyte-abctl-cron" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"airbyte":"cron", "<http://app.kubernetes.io/instance|app.kubernetes.io/instance>":"airbyte-abctl", "<http://app.kubernetes.io/name|app.kubernetes.io/name>":"cron"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable && failed to create patch: The order in patch list:...Sachit Kumbhat
08/26/2025, 7:38 AMč”å¾ę½®
08/26/2025, 7:43 AMPaul
10/05/2025, 7:12 AMRoberto Tolosa
10/07/2025, 4:07 PMJhonatas Kleinkauff
10/08/2025, 2:05 PMAadarsh Mahala
10/11/2025, 8:50 PMin OSS i am using "abctl local credentials" command but while using it the client-id and client-secret in calling <http://localhost:8006/api/public/v1/source> i am getting 401 unauthorized error why is that?Quang Nguyen
10/29/2025, 4:08 AMv3.0.x.
I'm using a pipeline from PostgreSQL ā BigQuery, and now the sync is failing with this error:
java.lang.ClassCastException: class io.airbyte.cdk.load.data.NullValue cannot be cast to class io.airbyte.cdk.load.data.TimestampWithoutTimezoneValue
(io.airbyte.cdk.load.data.NullValue and io.airbyte.cdk.load.data.TimestampWithoutTimezoneValue are in unnamed module of loader 'app')
This wasnāt happening before ā the sync worked fine when I were on a < 3.0.x version of the connector.
Unfortunately, downgrading isnāt an option at the moment because v3.0.x no longer uses the airbyte_internal dataset for temporary data storage, which weāve already removed/configured around.
Any ideas on how to work around this or if a patch is on the way?Jimmy Phommarath
11/10/2025, 7:19 PMunable to initialize local command: error communicating with kubernetes: unable to fetch kubernetes server version: Get "<https://127.0.0.1:46427/version>": EOF - error from a previous attempt: read tcp 127.0.0.1:51296->127.0.0.1:46427: read: connection reset by peerAdi Mizrahi
11/20/2025, 10:39 PMShailendra Jaiswar
12/30/2025, 2:06 PMLeslie Manrique
02/25/2026, 10:35 PMMatthias Hellmund
02/27/2026, 7:11 PMMichael
03/19/2026, 1:57 PMabctl on a kind (Kubernetes in Docker) provider, and we're hitting a consistent issue that breaks the main user account during the upgrade process.
Environment:
- Provider: kind
- Upgrade method: abctl local install with version flag
Issue:
During the upgrade, the process fails when trying to update the email for authentication:
INFO Using Kubernetes provider:
Provider: kind
Kubeconfig: /root/.airbyte/abctl/abctl.kubeconfig
Context: kind-airbyte-abctl
INFO Updating email for authentication
ERROR Unable to update the email address
ERROR unable to udpate the email address: failed to update organization: unexpected status code: 401
This error breaks the main/admin user, making the instance unusable after the upgrade.
Additional symptoms observed post-upgrade:
- Syncs appear to start but produce no log output in real time
- No errors are surfaced in the UI or logs when a sync is triggered
- Connectors show entitlement warnings in the logs (though these may be unrelated):
Connector entitlement not available. organizationId=OrganizationId(value=00000000-0000-0000-0000-000000000000)
What we tried:
- Incremental upgrades (minor version by minor version up to v2) ā earlier minor bumps work, but something breaks at the v2 boundary
- Upgrading connectors after the upgrade ā no improvement
- Multiple clean reinstalls/migrations ā same result
Has anyone else hit this 401 on the email update step? Is there a known workaround or a fix in the pipeline?
Important note:
The authentication corruption actually happens earlier than we initially thought ā not at the app v2.0.0 upgrade step, but already during the helm chart upgrade from 1.7.0 ā 2.0.5.
To be precise:
⢠Helm chart 2.0.5 still runs app version 1.7.0 (it only updates the installation method)
⢠But even at this first step, authentication data gets corrupted, before we even attempt the actual app upgrade to v2.0.0 (helm chart 2.0.18)
So the broken email/auth update (401) occurs as soon as the helm chart is bumped to 2.0.5, not when moving to app 2.0.0.
Other error that we got:
2026/03/19 14:21:14 [emerg] 1#1: host not found in upstream "airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl:80" in /etc/nginx/conf.d/default.conf:6
nginx: [emerg] host not found in upstream "airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl:80" in /etc/nginx/conf.d/default.conf:6
WARNING Back-off pulling image "airbyte/db:1.7.0"
WARNING Encountered an issue deploying Airbyte:
Pod: airbyte-db-0.189e44b17e6eeb4d
Reason: Failed
Message: Error: ImagePullBackOff
Count: 64
Thanks in advance!Kevin Lefevre
03/27/2026, 4:01 PMKevin Lefevre
03/30/2026, 4:43 PM3.7.2Ian Alton
04/06/2026, 7:41 PMDavid Robinson
04/13/2026, 9:41 AMAbhishek Batra
05/12/2026, 2:20 PMKevin Lefevre
06/18/2026, 8:03 AM2.1 from 03/04/2026, and still marked as Experimental version release :
This version of Airbyte is experimental. Airbyte changed the way we assemble new versions and haven't tested every feature and Helm chart configuration in version 2.1.0. If stability is your primary concern, you may elect to skip this version.
š do you plan to release a new official stable version ?
NB: interested by some feedbacks regarding stack Airbyte on GKE + Cloud SQL + GCS if someone upgraded to latest version šÅukasz Kieda
06/22/2026, 2:24 PM2.1 limits maximum allowed connections to 100. I canāt see this announced anywhere. Am I missing something?Erik Michal
06/23/2026, 1:47 PMkodanda ramudu
06/30/2026, 7:20 PMIan Alton
07/13/2026, 6:56 PMRichelle Herrli
07/27/2026, 5:07 PMIan Alton
08/11/2026, 11:39 PM