Repository navigation
Airbyte & Snowflake connector #45946
Unanswered
l-taranenko
asked this question in
Connector Builder
Replies: 2 comments
|
Have you tried to increase timeouts with values.yaml global:
env_vars:
HTTP_IDLE_TIMEOUT: 1800s
webapp:
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: internal
nginx.ingress.kubernetes.io/proxy-body-size: 16m
nginx.ingress.kubernetes.io/proxy-send-timeout: 1800
nginx.ingress.kubernetes.io/proxy-read-timeout: 1800and increase timeouts for load balancers? |
0 replies
|
Hi! This discussion hasn't had activity in over a year. Is this still relevant to you? If so, please reply and we'll keep it open. If we don't hear back within 14 days, we'll close this as part of our housekeeping. You can always reopen or create a new discussion later. Thanks! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have an issue connecting Airbyte which is hosted in GCP in Kubernetes and Snowflake trial account in GCP as well
We did all the steps provided in the airbyte guide https://docs.airbyte.com/integrations/destinations/snowflake
However, once we try the connection we have 502 error, which shown after the timeout
For example connection between airbyte and other SaaS tool (Chargebee) to pull the data from Chargebee works as expected
And we were able to connect Snowflake and Looker
Does anyone have ideas what can be wrong?
All reactions