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-worker : can't specify no_proxy variable #162

Closed
axinojolais opened this Issue Dec 20, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@axinojolais
Copy link

axinojolais commented Dec 20, 2016

Hi,

The kubernetes-worker charm has 2 config options related to proxying (http_proxy and https_proxy). However, there is no way to instruct the charm to not proxy some domains, which is generally done with the no_proxy environment variable.

Could this please be added ?

Thank you

@axinojolais

This comment has been minimized.

Copy link

axinojolais commented Dec 20, 2016

This is needed for example to use a docker registry deployed on the k8s cluster.

@mbruzek

This comment has been minimized.

Copy link
Contributor

mbruzek commented Dec 22, 2016

We can take a look at our priorities and add this feature to the list. Please provide us with your specific use case (config values) so we can test/verify.

If you don't want to wait for us to add it to our prioritized list, the code is open source and available here: https://github.com/juju-solutions/kubernetes/tree/master-node-split in the kubernetes/cluster/juju/layers/kubernetes-worker directory. Pull requests would be most welcome and may be faster than waiting on us to get to that feature request.

@axinojolais

This comment has been minimized.

Copy link

axinojolais commented Dec 27, 2016

My specific use case is that I want to deploy and use an image registry within my kubernetes cluster, and so I would like to avoid having to go through the proxy to fetch images on the kubernetes-worker units, since the registry is actually running on the worker units themselves.

If my private repository is hosted at kubernetes-registry.internal:5000, the option would take the value of "kubernetes-registry.internal".

Does that make sense ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment