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

Windows Nodes Cannot Utilize Authenticated Proxies #236

Open
HarrisonWAffel opened this issue Apr 11, 2024 · 0 comments
Open

Windows Nodes Cannot Utilize Authenticated Proxies #236

HarrisonWAffel opened this issue Apr 11, 2024 · 0 comments
Labels
enhancement New feature or request team/area2

Comments

@HarrisonWAffel
Copy link
Contributor

HarrisonWAffel commented Apr 11, 2024

When setting the HTTPS_PROXY and HTTP_PROXY agent environment variables in the Rancher UI, using an authenticated url will result in windows nodes failing to properly configure the proxy. This will lead to image pull failures for the rke2 runtime image, preventing the node from becoming available. This is due to the use of netsh in the wins install script.

https://github.com/rancher/wins/blob/070f0147403142ba616d09b37bfd696d00a8b3d9/install.ps1#L632-L638

The expected format for an authenticated proxy is http(s)://USERNAME:PASSWORD@HOST:PORT, and netsh will return an error whenever more than 1 colon is found in the value.

We likely need to utilize windows credential manager to properly configure the credentials for a given proxy host, and then strip the authentication info from the environment variables before calling netsh

@HarrisonWAffel HarrisonWAffel added the enhancement New feature or request label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request team/area2
Projects
None yet
Development

No branches or pull requests

1 participant