Airbyte Upgrade Issues with External Postgres (GCP) on v1.6.0 → v1.8.0

[wasimb-atica]

Setup

1. Airbyte all three databases dumped and restored from AWS RDS(previous) to GCP CloudSQL(now with previous dump).
2. Deployment via Helm chart v2.x
   Upgrading from Airbyte v1.6.0(On AWS EKS) → v1.8.0(Trying on GCP GKE)

Expected Behavior

• Airbyte server should start and connect successfully to the external Postgres DB.
• Existing sources/destinations should be visible and functional.
• Connection tests for sources/destinations should succeed.

Actual Behavior

• v1.6.0: UI loads, but page displays 401 Unauthorized. (Helm Airbyte Chart version 2.0.9)
• v1.7.0+: Server starts but UI shows database connection/access errors when pointed to new external Postgres(GCP CloudSQL). (Helm Airbyte Chart version 2.0.9)
• v1.8.0 (or default): Server starts successfully, existing connections, connections job history, sources and destinations are visible but connection tests fail with: (Helm Airbyte Chart version 2.0.9)

Airbyte is temporarily unavailable. Please try again. (HTTP 502)

Question / Possible Root Cause

Could this issue be related to missing or incompatible temporal and temporal_visibility databases after migration?
Would recreating these empty databases resolve the 502 error on v1.8.0?