You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expectation is that proxies required by the node are defined by the user shell/service shell, and are set in a global location on the node. If the user has the corresponding HTTP_PROXY etc. environment variables set, they should be set for the system agent.
It's important to note that Rancher doesn't really support communication-through-proxy in the first place, due to potential performance implications. We don't want to open WATCH requests through a corporate proxy for example.
It appears that the installer is overwriting the .env file at
https://github.com/rancher/system-agent/blob/main/install.sh#L804
This is causing issues with a few users who are behind a corporate proxy. Is there a way to set a proxy to be used when defining a cluster?
The text was updated successfully, but these errors were encountered: