-
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 Fails Due to Valid Argument #354
Comments
Just noticed there is a potential fix noted in #345 I'll leave this open until 1.7.2 hits epel repo and there is a chance to try it out. |
I'm also getting this! |
I have a fix for this up that will be in v1.7.3. v1.7.2 might work for you as well. |
@plombardi89 FYI kubeadmn |
Hey @plombardi89, were you able to confirm that kubeadm 1.7.3 fixes this issue for you? |
@pipejakob I have not confirmed. I might have some time tomorrow to give it a whirl. |
Closing this as it should be fixed with v1.7.3, reopen if not |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened: Running
kubeadm init --config=<path>
fails.What you expected to happen:
kubeadm init --config=<path>
configures based on the provided file.How to reproduce it (as minimally and precisely as possible):
Create a file
/tmp/kubeadm.yaml
with the below content:Run
kubeadm init --config=/tmp/kubeadm.yaml
Get error:
Anything else we need to know?:
Environment:
Kubernetes version (use
kubectl version
): NACloud provider or hardware configuration**: AWS
OS (e.g. from /etc/os-release): CentOS 7.3 1703_01
Kernel (e.g.
uname -a
): Linux ip-10-10-0-216.ec2.internal 3.10.0-514.26.2.el7.x86_64 kubeadm join on slave node fails preflight checks #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/LinuxInstall tools:
Others: Kubeadm Version =
kubeadm version: &version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.1", GitCommit:"1dc5c66f5dd61da08412a74221ecc79208c2165b", GitTreeState:"clean", BuildDate:"2017-07-14T01:48:01Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
The text was updated successfully, but these errors were encountered: