Timeout issue when creating source or destination connectors on Airbyte deployed on AWS EKS via Helm

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

Summary

User is facing a timeout issue when creating source or destination connectors on Airbyte deployed on AWS EKS via Helm. The issue occurs before K8s can pull the connector containers. User specifically mentions MySQL & Redshift connectors. User is looking to see if the timeout is configurable.


Question

Hello. I am trying to deploy airbyte on AWS EKS via Helm. The airbyte stack comes up and the web UI is accessible. The issue I am running into now is that when creating a source or destination, the test times out before K8s can even pull the connector containers.

The specific connectors are MySQL & Redshift, though I suspect others will have the same issue.

Is that timeout configurable somewhere that I’m just not seeing in the documentation?


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

["timeout-issue", "source-connector", "destination-connector", "airbyte", "aws-eks", "helm", "mysql-connector", "redshift-connector", "timeout-configuration"]