Summary
When deploying Airbyte on Kubernetes using helm charts and setting HTTP_PROXY configurations, the read and write pods do not inherit the environment variables for HTTP proxy, causing issues with accessing APIs on the internet. The problem persists even with the latest Airbyte helm chart version.
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 <Issues · airbytehq/airbyte · GitHub 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.