502 error when creating source on Airbyte deployed to GKE using Helm

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Request times out with 502 error code when creating a source on Airbyte deployed to GKE using Helm. Works fine locally with an external database. Cluster configuration: 3 nodes, each with 8gb RAM and 2 vCPUs.


Question

Hi everyone!

I just deployed Airbyte to GKE using helm.
When I’m trying to create a source the request times out with 502 error code every time.

I’m using an external database. Everything works fine locally.

Cluster configuration:
3 nodes
Each node has 8gb ram and 2vcpus

Has anyone faced this issue before?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["502-error", "source-creation", "airbyte", "gke", "helm", "timeout", "external-database", "cluster-configuration"]
2

Do you have any errors in logs for pods?

3

Could you please tell me which pods I have to check?

4

usually server and worker and the most interesting, but check all of them

5

quite often I use stern https://github.com/stern/stern and check for any issues

6

I run stern --tail 0 . and repeat some actions to see errors