https://linen.dev logo
Join Slack
Powered by
Status: Resolved by the release of Airbyte 2.3 :r...
# announcements
r
Status: Resolved by the release of Airbyte 2.3 🚨 OSS Airbyte deploys might be failing since the official MinIO image has been removed. We're actively working on fix right now. I will offer updates in the thread.
👍 2
👀 2
A chart fix is on the way. Until then, you can use the following workaround: NEW INSTALLS add this override:
Copy code
helm install airbyte airbyte-v2/airbyte \
    --namespace airbyte --create-namespace --version 2.2.0 \
    --set minio.image.repository=airbyte/minio
EXISTING INSTALLS Run in this order. Don't run the helm upgrade first; it fails while MinIO is down. 1.
Copy code
kubectl -n airbyte set image statefulset/airbyte-minio \
     airbyte-minio=airbyte/minio:RELEASE.2023-11-20T22-40-07Z
2.
Copy code
kubectl -n airbyte delete pod airbyte-minio-0
   kubectl -n airbyte delete pod airbyte-minio-create-bucket --ignore-not-found
   (required — the StatefulSet rollout stalls on a stuck pod)
3.
Copy code
helm upgrade airbyte <repo>/airbyte \
     --namespace airbyte --reuse-values \
     --set minio.image.repository=airbyte/minio
If step 3 fails on a 
minio
hook, just re-run it. Keep the image tag unchanged.
octavia loves 1
a
Okay, workaround is working on my gcp stack Thanks
j
@Richelle Herrli Thanks for the quick update on this. Just to define scope a bit, do you happen to know if this fails even for people with the 
minio
chart disabled (e.g. when using Google Cloud Storage or S3 for state/log storage)? Or do those checks happen before that gets evaluated?
r
Good callout! This should not affect you if the MinIO chart is disabled
👍 1
i
Version 2.3 is out with the fix for the MinIO removal. docs.airbyte.com/release_notes/self-managed/v-2.3
❤️ 2
octavia loves 3
v
A possible replacment for minio github.com/versity/versitygw
👀 1
Open in Slack
PreviousNext
Powered by