Source Connection pod failed to connect the worker

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: GKE 1.21.14-gke.7100
  • Memory / Disk: Default
  • Deployment: K8s using Helm
  • Airbyte Version: 0.43.22
  • Source name/version: MySQL
  • Destination name/version:
  • Step: The issue is happening during creating the connection.
  • Description:
    I have been trying to deploy Airbyte in K8s env using helm chart. I could deploy all modules successfully by removing the istio proxy container in each pod (created due to some policies in our K8s cluster).
    When I create a new source connection then a pod is created with a default proxy container. The default container causes issues to connect the worker module. However, the default container can be removed by applying annotations. I don’t identify the pod templates where I can apply those annotations.

So, I would like to know the following queries.

  • Which module creates a connection pod?
  • Where is the pod template defined in the helm chart for the connections?

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 Team,
Is there a way to disable the sidecar injection in the pod creation by the worker job?

Hello Shail, it’s been a while without an update from us. Are you still having problems or did you find a solution?

Hi there,
I am still having same issue. I have tried to set annotation for the variable JOB_KUBE_ANNOTATIONS. But didn’t work.