MAS CLI version
19.7.0
CLI function used
install
What happened?
There is a problem in the Kubernetes Python Client library (which is used by your ansible scripts) -> kubernetes-client/python#2520
It seems that previous versions of that library where ignoring http(s)_proxy and no_proxy environment variables, while the newer versions only ignore the no_proxy variable.
This leads a problem, where some pods (e.g. ibm-sls-controller-manager) are trying to access a local api via proxy (even if localhost is set in no_proxy) and ran into a time-out, which causes the installation pipeline to fail.
We ran into this issue during installation of MAS v9-260226 with a recent installer (e.g. 19.7.0), but it seems to me that all installer versions since the end of 2025 are affected.
For our client, we were able to install an older MAS version with an older installer (17.2.0) where the library was ignoring both http(s)_proxy and no_proxy.
This is more an issue of the container images you are using, than with the CLI itself, but since its affecting installation/update of MAS via CLI in environments with a proxy, I'm posting it here.
Steps to reproduce and a workaround are already mentioned in:
kubernetes-client/python#2520
Relevant log output
MAS CLI version
19.7.0
CLI function used
install
What happened?
There is a problem in the Kubernetes Python Client library (which is used by your ansible scripts) -> kubernetes-client/python#2520
It seems that previous versions of that library where ignoring http(s)_proxy and no_proxy environment variables, while the newer versions only ignore the no_proxy variable.
This leads a problem, where some pods (e.g. ibm-sls-controller-manager) are trying to access a local api via proxy (even if localhost is set in no_proxy) and ran into a time-out, which causes the installation pipeline to fail.
We ran into this issue during installation of MAS v9-260226 with a recent installer (e.g. 19.7.0), but it seems to me that all installer versions since the end of 2025 are affected.
For our client, we were able to install an older MAS version with an older installer (17.2.0) where the library was ignoring both http(s)_proxy and no_proxy.
This is more an issue of the container images you are using, than with the CLI itself, but since its affecting installation/update of MAS via CLI in environments with a proxy, I'm posting it here.
Steps to reproduce and a workaround are already mentioned in:
kubernetes-client/python#2520
Relevant log output