@kapa.ai i am upgrading from 1.8 to 2.0.1 community. do i also need to do backup for object storage (gcs)?

Based on the knowledge sources, when upgrading from 1.8 to 2.0 (Community), the backup guidance focuses specifically on Airbyte's internal Postgres database — there is no mention of needing to back up object storage (GCS). The documentation states: > "If you haven't configured an external database, you must backup Airbyte's internal Postgres database. If you fail to do this, and something goes wrong during your upgrade, you could lose all your connections and states." [Helm chart V2 upgrade guide] There is no mention in the knowledge sources of needing to back up GCS (or any object storage) as part of the upgrade process. The object storage (GCS) holds logs, state, and workload output — and since it's external and managed independently of the Helm chart, it is not something you need to back up as part of this upgrade. In summary: You only need to back up the internal Postgres database (if you're not using an external database). No GCS backup is required or mentioned for this upgrade. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

what part of values.yaml i need to keep while upgrading from 1.8 to 2.0?

This error occurs because the

airbyte-config-secrets

Kubernetes secret in your

airbyte-v2

namespace is missing the

AB_INSTANCE_ADMIN_CLIENT_ID

key, which is required by the Helm chart.

AB_INSTANCE_ADMIN_CLIENT_ID

maps to

global.auth.instanceAdmin.clientId

in the V2

values.yaml

. [values.yaml reference] You need to add this key (along with other required auth-related keys) to your

airbyte-config-secrets

secret. You can patch the existing secret:

kubectl patch secret airbyte-config-secrets -n airbyte-v2 \
  --type merge \
  -p '{"stringData": {"AB_INSTANCE_ADMIN_CLIENT_ID": "<your-value>"}}'

Or recreate/update it using a YAML file:

apiVersion: v1
kind: Secret
metadata:
  name: airbyte-config-secrets
type: Opaque
stringData:
  AB_INSTANCE_ADMIN_CLIENT_ID: "<your-value>"
  # add other required keys here

Apply it with:

kubectl apply -f secrets.yaml -n airbyte-v2

[Preconfiguring Kubernetes Secrets] Also note a related known issue: Helm chart V2 also requires an

AIRBYTE_DUMMY_SECRET

key to exist in the secret (used internally by the chart). If you haven't added it yet, you may hit that error next. You can add it at the same time:

kubectl patch secret airbyte-config-secrets -n airbyte-v2 \
  --type merge \
  -p '{"stringData": {"AB_INSTANCE_ADMIN_CLIENT_ID": "<your-value>", "AIRBYTE_DUMMY_SECRET": "dummy"}}'

Make sure all other required keys for your integrations are also present in the secret before deploying. 👍 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 do i need to copy it from my 1.8 deployment?

Based on the conversation context, you're asking whether you need to copy the

AB_INSTANCE_ADMIN_CLIENT_ID

(and related auth secrets) from your existing 1.8 deployment. The knowledge sources do not explicitly address whether to copy existing auth secret values from a V1 deployment. However, here's what is documented: • In Helm chart V2,

AB_INSTANCE_ADMIN_CLIENT_ID

maps to

global.auth.instanceAdmin.clientId

. [values.yaml reference] • The upgrade guide recommends deploying into a new namespace with a fresh values and secrets file when using an external database. [Helm chart V2 upgrade] • If you don't supply your own client ID/secret, Airbyte can auto-generate auth credentials. You can retrieve them after deployment with: [Authentication docs]

kubectl get secret airbyte-auth-secrets -n airbyte-v2 -o yaml

In practice: Since this is a fresh namespace deployment, you don't necessarily need to copy the old values — you can let Airbyte generate new credentials. However, if you want to preserve the same client ID/secret (e.g., for API integrations that depend on them), you would need to retrieve them from your 1.8 deployment and supply them in the new secret. The knowledge sources don't go further than this on the topic, so I'd recommend checking your 1.8 secrets if continuity matters to you:

kubectl get secret airbyte-airbyte-secrets -n airbyte -o jsonpath='{.data}'

👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.