Summary
User reports an issue with HTTP_PROXY environment variables not being inherited by read and write pods in Airbyte deployed on Kubernetes using helm charts. The issue persists across different helm chart versions.
Question
Hey all! I’ve deployed Airbyte on Kubernetes using helm charts. However, I need to set HTTP_PROXY settings to access APIs on the internet. I set configurations as described in <https://github.com/airbytehq/airbyte/issues/3076|this issue> and it works smoothly for check and discover pods. However, when Airbyte creates pods for read and write steps, these pods do not have the environment variables for HTTP proxy. So, read and write pods do not inherit variables. I have Airbyte helm chart version 0.53.3. I also tried with the latest version but the problem still continues. Has anyone faced with this issue before?
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.