Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpfman-operator/agent and Egress Proxy Support #115

Open
frobware opened this issue Aug 27, 2024 · 1 comment
Open

bpfman-operator/agent and Egress Proxy Support #115

frobware opened this issue Aug 27, 2024 · 1 comment
Milestone

Comments

@frobware
Copy link
Contributor

In clusters using an egress proxy, it is crucial to ensure that bpfman-operator and bpfman-agent respect the http_proxy and no_proxy environment variables. This will determine whether these components can successfully communicate through the proxy.

At https://curl.haxx.se/docs/manual.html there's description of environment variables related to using HTTP proxy which libcurl/curl understands:

ENVIRONMENT VARIABLES

Curl reads and understands the following environment variables:
http_proxy, HTTPS_PROXY, FTP_PROXY

They should be set for protocol-specific proxies. General proxy should be set with
ALL_PROXY

A comma-separated list of host names that shouldn't go through any proxy is set in (only an asterisk, '*' matches all hosts)
NO_PROXY

If the host name matches one of these strings, or the host is within the domain of one of these strings, transactions with that node will not be proxied.

Please notice that http_proxy is spelled lowercase as the only one among these variables. Some libraries/programs look for lowercase names of these variables whereas others look for upppercase names. To be safe one should define both lowercase and uppercase versions of each variable.

@github-project-automation github-project-automation bot moved this to 🆕 New in bpfman Aug 27, 2024
@anfredette anfredette added this to the Q4-2024 milestone Aug 29, 2024
msherif1234 pushed a commit to msherif1234/bpfman-operator that referenced this issue Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants
@frobware @anfredette and others