Replication Job Pod Taints and Tolerations in Airbyte Helm Deployment on EKS

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

Summary

Replication job pod in Airbyte Helm deployment on EKS not following defined taints and tolerations. Question about expected behavior and potential missing configurations.


Question

Hi team , When deploying airbyte with helm in eks, I’ve observed that the replication-job pod which gets created while running a sync for connector doesn’t follow the taints & tolerations defined for all pods. Is that expected to be scheduled inside another node by default? Am i missing something?


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

["replication-job-pod", "taints", "tolerations", "airbyte", "helm", "eks", "node-scheduling"]
2

Sounds related to https://github.com/airbytehq/airbyte/issues/28389

3

Do we have a fix for it? , I’ve tried adding another node group and it works scheduled on another node :smiley: