Issue with `tolerations` not being applied to temporary pods in Airbyte Helm deployment

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

Summary

Temporary pods generated by Airbyte are correctly applying nodeSelector but not tolerations in both jobs and temporary sources/destinations, causing scheduling problems on expected nodes.


Question

hello all
I am facing an issue with the temporary pods generated by Airbyte. When configuring the nodeSelector and tolerations in the Helm templates, the temporary pods are correctly applying the nodeSelector, but the tolerations are not being applied. This issue occurs in both jobs (global.jobs.kube) and temporary sources and destinations (workload-launcher), causing scheduling problems on the expected nodes.

• Configure the nodeSelector and tolerations in the Airbyte deployment templates using Helm.
• Run a sync or task that generates temporary pods, including jobs and temporary sources/destinations.
• Observe that the nodeSelector is correctly applied to the temporary pods, but the tolerations are not.

  jobs:
    resources:
      requests:
        memory: 256Mi
        cpu: 250m
      limits:
        memory: 2Gi
        cpu: 3000m
    kube:
      nodeSelector: *selectorNodePoolEfopDados
      tolerations: *tolerationNodePoolEfopDados
      labels: *labels

workload-launcher:
  nodeSelector: *selectorNodePoolEfopDados
  tolerations: *tolerationNodePoolEfopDados
  podLabels: *labels```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1723735183126089) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte", "temporary-pods", "helm-templates", "nodeSelector", "tolerations", "scheduling-problems"]
</sub>
2

I dont’ have an answer for you but I am facing the same issue. The orchestrator pod specifically is not getting the tolerations I have setup and so never get scheduled and my connections fail because of it.

3

This was the github issue that seems to document it: https://github.com/airbytehq/airbyte/issues/28389

4

ALthough the ticket might be being ignored because it references and older version which may or may not have actully had this same exact issue.