Hi all, I'm encountering a discrepancy between Airbyte Cloud and my Local Open Source instance while configuring a GCS Data Lake connection. • The Issue: Using the exact same configuration, the connection is successful on Airbyte Cloud, but fails on my local instance. • Error Message on Local:

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

• Environment: Airbyte running on Docker. • What I've checked: The Service Account JSON key is identical. Network connectivity seems fine, but the UI keeps throwing the 502 error during the "Test Connection" phase. Has anyone faced this issue where the local fails to communicate during a GCS setup despite the config being valid? Any logs I should specifically look into to debug this further? Thanks in advance for the help!

502s during connection check or schema discovery are often due to HTTP timeouts. I'd suggest trying to merge these config values into your `values.yaml`:

global:
  env_vars:
    HTTP_IDLE_TIMEOUT: "30m"
    READ_TIMEOUT: "30m"

If you're using a custom ingress (e.g. your nginx or a cloud load balancer) you may need to also increase the timeouts there.