Kubernetes Worker charm does not pick up the default proxy settings defined in the model, I.E juju-https-proxy and juju-http-proxy

[Calvin Hartwell]

Hi all,

The kubernetes-worker charm does not pickup the default proxy settings defined in the model like most charms should now. These options are juju-https-proxy and juju-http-proxy.

The proxy settings in the charm should use the juju values as defaults which we can override if we require. For example, if we have a local registry on-prem which we do not want to access through the proxy, we should be able to override the proxy settings of the kubernetes-worker to disable the http/https proxy for the docker daemon/container run-time.

We encountered an issue recently during a customer deployment where we expected the proxy settings to be set and the containers were not being pulled, so we had to go set these settings.

I hope this is pretty self-explanatory, feel free to ask questions.

Cheers,

- Calvin

[Calvin Hartwell (calvinh)]

FYI this is a low-priority item as it is easy to work around, but it should be fixed long-term.

[Peter Jose De Sousa (pjds)]

This bug requires changes in three places in order to resolve. Created a test plan for this: https://docs.google.com/spreadsheets/d/1FR6pFcdPLR4PAlWuOfBvJmmcfpFz6W8DVa4gXUPAVoo/

[Tim Van Steenburgh (tvansteenburgh)]

Hey Peter, can you please add a comment with links to all the Github PRs that go with this bug?

[Peter Jose De Sousa (pjds)]

Sure,

https://github.com/juju-solutions/layer-docker/pull/138
https://github.com/charmed-kubernetes/charm-docker/pull/7
https://github.com/charmed-kubernetes/charm-containerd/pull/8
https://github.com/charmed-kubernetes/jenkins/pull/447
https://github.com/charmed-kubernetes/jenkins/pull/456

Cheers!

[Peter Jose De Sousa (pjds)]

Apologies and one more:

https://github.com/charmed-kubernetes/layer-container-runtime-common/pull/4