Summary
User is seeking help to pass proxy environment variables to Airbyte connector sidecar pods, detailing previous attempts and current setup.
Question
Hi <@U01MMSDJGC9> and everybody!
Subject: Help Needed: Passing Proxy Variables to Connector Sidecar Pods in Airbyte
Hi everyone,
I’m facing an issue with passing proxy variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY) to the connector sidecar pods in Airbyte. Despite trying multiple solutions from the existing GitHub issues and documentation, I haven’t had success so far.
Here’s the situation:
• When I test connectivity using curl -x <proxyip:port> from within the connector sidecar pod, it works perfectly and reaches the desired external service.
• The rest of my setup, including the worker and other components, is likely complete and working as expected.
The only missing piece is ensuring the proxy environment variables are passed correctly to the connector sidecar pods during execution.
What I’ve Tried So Far
• Adding proxy variables to env_vars in the values.yaml file (global, worker, jobs.kube.env).
• Using extraEnv under relevant sections.
• Setting CONTAINER_ORCHESTRATOR_ENABLED=false to allow JOB_DEFAULT_ENV_* variables to be inherited by dynamically created pods.
While global proxy variables seem to work for other pods, the connector sidecar pods still don’t inherit the proxy variables.
Question
How can I pass proxy variables to the connector sidecar pods? If there’s a configuration I’ve missed or a known workaround for this, I’d greatly appreciate your guidance!
Thank you in advance for your help!
HELP 
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.