Helm Chart Configuration for MySQL Source Timeout Issue

Summary

User deployed Airbyte on GKE using Helm and encountered a timeout error while testing a MySQL source. They seek guidance on adjusting the BASIC_AUTH_PROXY_TIMEOUT in the Helm chart and inquire about potential other causes for the error.


Question

Hi, I deployed Airbyte on gke cluster using helm.
However, I encountered an error below while defining and testing a mysql source.
I looked up the error and it seems to be a timeout issue, and I think I can increase the BASIC_AUTH_PROXY_TIMEOUT value, but that value is only used in docker, so how can I adjust it in the official helm chart?
Or if it’s not a timeout issue, is there something else you suspect?
Unknown error (http.504`....)



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

['gke', 'helm', 'mysql-source', 'timeout', 'basic-auth-proxy-timeout']