Issues with Airbyte connection setup

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

Summary

Issues with replication job init container not inheriting configured requests and limits, and pod not inheriting imagesecretpull from configmap


Question

Hi all, when I set up connections with Airbyte I have noticed 2 things:

the replication job (main job?) the init container does not have configured by default requests and limits despite if you add them for the JOB MAIN variables
The pod does not seem to inherit the imagesecretpull that has been configured in the configmap

I am wondering if I am just have something misconfigured or if it’s expected?


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

["airbyte", "connection-setup", "replication-job", "init-container", "pod", "imagesecretpull", "configmap"]
2

My current solution was to modify the source code and rebuild the worker image but I have hardcoded the init requests and limits and likewise the imagepullsecret

3

Could you share some of the relevant config and also include details about how you’re deploying Airbyte and your current Airbyte version? That might help get better answers