Skip to content
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

kubeadm init should provide a HTTP_PROXY configure #182

Closed
netroby opened this issue Feb 26, 2017 · 9 comments

Comments

Projects
None yet
7 participants
@netroby
Copy link

commented Feb 26, 2017

We are living in china. our network can not reach gcr.io. so while try to using kubeadm init to create kubernetes cluster. we will failed to create containers.
Because Greate firewall blocked gcr.io and the all google service domain.

So please let kubeadm support a configure argument (which support HTTP_PROXY)

Download image through proxy seems a only one solution for us. or we can not using kubernetes

@bruceauyeung

This comment has been minimized.

Copy link
Member

commented Feb 27, 2017

kubeadm will try to download kubenetes components and etcd images if they don't exist.These images by default will be pulled from gcr.io/google_containers, but you can pull them from any repository by setting environment variables KUBE_REPO_PREFIX, KUBE_DISCOVERY_IMAGE, KUBE_ETCD_IMAGE, please refer to https://kubernetes.io/docs/admin/kubeadm/

@netroby

This comment has been minimized.

Copy link
Author

commented Feb 27, 2017

I know that section. but this is not about my issue.
set up that ENV Vars not as quick as configure a proxy for kubernetes.

Just one command can save much time

kubeadm init --with-proxy=http://10.0.19.28:8080 

If with these flag. kubeadm will configure proxy global for the master/join node. and exclude the node master ip for us automatic.

Should make things easier

@xilabao

This comment has been minimized.

Copy link

commented Feb 27, 2017

@netroby In fact, kubeadm support http proxy. see https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/master/manifests.go#L426
set http_proxy as environment variable, it could work.

@netroby

This comment has been minimized.

Copy link
Author

commented Feb 27, 2017

Ok. I guess we can update the document for more details

@yuvipanda

This comment has been minimized.

Copy link

commented Apr 18, 2017

Should this issue be closed now?

@netroby netroby closed this Apr 18, 2017

@netroby

This comment has been minimized.

Copy link
Author

commented Apr 18, 2017

closed

@lastboy1228

This comment has been minimized.

Copy link

commented Sep 15, 2017

If you set http_proxy as environment variable when execute "kubeadm init", the env variable will be recorded in the files in /etc/kubernetes/manifests/.

@TodayyadoT

This comment has been minimized.

Copy link

commented May 4, 2018

@xilabao the link you attached above didn't exist now

@lastboy1228 I have set http_proxy and then execute 'kubeadm init', but it didn't record in /etc/kubernetes/manifests/

@netroby how did you solve this at last? Wo yeshi tianchao zimin。

@outception

This comment has been minimized.

Copy link

commented Mar 6, 2019

sudo http_proxy=192.168.99.1:1080 kubeadm init
this work for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.