-
Notifications
You must be signed in to change notification settings - Fork 706
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" not possible on restricted network #292
Comments
Hi @rschoultz! It is possible to deploy kubeadm without internet. You have to prepull the required master images for the version of choice in beforehand though. Sorry that the However, you might skip the check by passing a valid semver kubernetes version directly like this:
I noticed that you used I'm taking a pass at docs currently, and I will incorporate this feedback to address this. Also we should give a much more user-friendly output of the command in this situation. Hope this helps and thanks for using kubeadm 😄! |
OK, yes, I had tried the --kubernetes-version flag as well, I thought, but I did not supply it correctly, as I had indicated "1.6.4" and not "v1.6.4". The reason for using --skip-preflight-checks was just for trying out various potential options for working around the problem. |
facing the same issue, in envs with proxy:
If I set the proxy, there are 2 issues:
In the hope that it won't use IP address, but hostnames, I tried the below, but for some reason it's still working with IP addresses :(, and the NO_PROXY is not able to skip them, as no_proxy does not work with wildcards...
As a workaround, for now I have set NO_PROXY for each IP address individually.
Note: should anyone plan to use proxy with kubeadm, being a go application, honors only NO_PROXY environment variable, and ignores the no_proxy (lowecase). (see golang/go#13456 ) To replicate this issue with 1.6.4, one can use: https://github.com/ReSearchITEng/kubeadm-playbook |
You can set cc @kad |
Digging further, it seems my issue comes from |
@ReSearchITEng |
@luxas Taking priority would be ok, but it's completely ignoring the cli arguments. |
@ReSearchITEng That's due how to the API machinery in Kubernetes works, I'm sorry. Therefore, we've added better validations for such cases in v1.7 |
@ReSearchITEng btw, golang respects both upper and lowercase *_proxy variables. you can see how it's done here: https://github.com/golang/go/blob/master/src/net/http/transport.go#L266 and https://github.com/golang/go/blob/master/src/net/http/transport.go#L568 Regarding |
As part of issue kubernetes/kubeadm#292 discussion, it turned out that for users it is not always obvious that version specification parameter must be in form "vX.Y.Z". This patch allows to specify it in form "X.Y.Z" and converts it internally to normal semantic version which expected in the rest of the code.
Automatic merge from submit-queue (batch tested with PRs 48196, 42783, 48507, 47719, 46138) kubeadm: Allows to use versions like 1.6.4 instead v1.6.4 **What this PR does / why we need it**: As part of issue kubernetes/kubeadm#292 discussion, it turned out that for users it is not always obvious that version specification parameter must be in form "vX.Y.Z". This patch allows to specify it in form "X.Y.Z" and converts it internally to normal semantic version which expected in the rest of the code. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: **Special notes for your reviewer**: **Release note**: ```release-note - kubeadm now can accept versions like "1.6.4" where previously it strictly required "v1.6.4" ```
Kind of fixed with kubernetes/kubernetes#48507 |
This is a...
Problem:
Starting in version 1.6.x, it is not possible to run "kubeadm init" from a private network, i.e. where the host is not allowed to access Internet, as kubeadm get stuck on trying to retrieve a stable-1.6.txt file:
I have, of course, tried with flag combinations like "kubeadm init --skip-preflight-checks --kubernetes-version=stable-1.6.4", but it seems like kubeadm from some version 1.6.x cannot run without access to the Internet.
Proposed Solution:
Please make the access to external services optional.
This is on using version 1.6.4:
Versions
Environment:
kubectl version
): 1.6.4uname -a
): Linux *** 3.10.0-327.36.3.el7.x86_64 kubeadm join on slave node fails preflight checks #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux**Moved from where originally registered in kubernetes/website#4019
The text was updated successfully, but these errors were encountered: