How to speed up source connection test in kubernetes?

  • Is this your first time deploying Airbyte?: Yes
  • Deployment: Are you using Docker or Kubernetes deployment? Kubernetes on GKE Autopilot
  • Airbyte Version: What version are you using now? 0.40.26
  • Step: The issue is happening during sync, creating the connection or a new source? Creating new source
  • Description: I would like to know if there is a way to speedup the source connectivity tests in airbyte? There is a pod that is created to do this job once we send an API request to test the source, but the main question is if there is a way to speed up that test? on a local k8s it takes around 10 seconds, in GKE Autopilot it takes around 30 seconds, and on Airbyte Cloud around 7 seconds.
    Is there a parameter that could be tweaked for that?

Thank you

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hey @khaledalarja! Thanks for your patience - I was out last week for the holidays and am catching up with messages now.

There is no parameter that can be currently tweaked.