-
Notifications
You must be signed in to change notification settings - Fork 140
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
Proxy param does not accept authentication header #55
Comments
Hi @senpai-d |
Hi @abikouo , I have installed the collection locally to test it out and the proxy_headers variable was picked up but it still returned an authentication required. Does the username:password need to be encoded or anything? Thanks. |
@senpai-d could you please display the version of the kubernetes python api you are using ?
please also try to use |
@senpai-d using this simple playbook I can talk to the kubernetes api via proxy.
|
We have tried 1.12 and 1.17 for the kubernetes client version. We have got it to work with k8s_info successfully, but when we use k8s, the connection times out. We aren't sure if it is proxy related, but we use the same host for k8s_info and k8s, but only k8s_info seems to work. |
@senpai-d thats strange, on our side it is working for both module as it is the same api used. could you please check that it is related to your proxy ? |
SUMMARY
When setting a proxy url in the proxy param, the username:password header is not read. It only accesses the URL, which returns a 407 if authentication is required for the proxy.
ISSUE TYPE
COMPONENT NAME
k8s
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
WSL Ubuntu 18.03
Pythion 3.6 virtual environment
STEPS TO REPRODUCE
With a proxy url such as http://USERNAME:[email protected]:3001, the USERNAME:PASSWORD header is not loaded in, resulting in a 401 due to authentication required with proxy.
EXPECTED RESULTS
Expected for the namespace to be created.
ACTUAL RESULTS
Received a 407 from proxy server.
The rest of the output is proxy server error being returned.
The text was updated successfully, but these errors were encountered: