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
kubernetes_asyncio major version release breaks: NO_PROXY env var not honoured #420
Comments
Thanks for raising this. If we pinned |
Yes. In my deployment I pinned it to 21.7.* (which is the last release before 22) and it solved the problem. Please notice though that I am using 2021.3.1 version of |
Just came here to post this issue. I'm on AKS. Workaround was downgrading the
I have tons of examples. this was the error I got
|
Could you try |
I'll do it when I get to work this AM.
UPDATE:I confirmed that latest version works! |
This project no longer uses |
What happened: dask-kubernetes cannot connect to K8s API when HTTPS proxy is used in the system.
I have
HTTPS_PROXY
,https_proxy
,HTTP_PROXY
andhttp_proxy
environment variables set. They point to Squid proxy.I also have
NO_PROXY
env var set, which contains172.20.0.0/16
.This configuration used to work - dask-kubernetes was able to communicate with K8s API, not going through proxy. Now it tries to go through proxy. This fails, because proxy is outside of the cluster (IIUC, dask-kubernetes with the default in-cluster config connects to K8s API via internal endpoint, not through public internet). I am getting this traceback:
This seems to be related to recent update of
kubernetes_asyncio
to major version 22. They state in the changelog:What you expected to happen: NO_PROXY env var should be honoured. Connection should not go through proxy.
Minimal Complete Verifiable Example:
I can come up with it later.
Anything else we need to know?:
Environment:
dask-kubernetes
installed via pip,dask
installed via condaThe text was updated successfully, but these errors were encountered: