-
Notifications
You must be signed in to change notification settings - Fork 701
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 with no ipv4 address on the network interface with defaultroute #1156
Comments
@scheuk what's the local resolvable IPv4 address for that host? /cc @kubernetes/sig-network-bugs |
@timothysc do we know if the api-server will work with this kind of environment? I'm just wondering if we get kubeadm to work in this network setup, are we going to run into more problems down the road? |
If you have a specific ethernet adaptor that wraps the details and you can bind to, or /etc/hosts override I would think it should "just work". |
@timothysc
the I've spent the morning making
However I'm still stuck needing a route to perform both the |
@timothysc I just attempted to add |
So this has todo with the specifics of your networking configuration, coupled with the default behavior of the system. I'm fairly certain if you were to make a bridged adapter to bind the IPv4 address to, vs. being bound to loopback, it would detect properly. I'm digging right now to see if there is a global override for the nic that works across *. |
So it would be a combination of --api-advertise-addresses and --hostname-override , I'm not certain all those options percolate to all the subcommands, still digging. |
@scheuk could you run
with your config file specifying: advertiseAddress |
You may need to pass in |
you can run A possible work around for the images pull thing given the config would be something like: |
No go on --kubeconfig:
also if I try with --config it says you can't combine those two:
This worked, I'll update my deployment to do this
|
I mean that you can use |
is a minor bug that we can fix in 1.13 Are you still blocked? |
I am still blocked. Thanks for all the help so far! |
The output of |
This normally done in ansible as the token is short lived and it's easier to capture the join command output from token create rather than init. |
Also it's a little bit harder to parse with all the other output and spacing ;) |
I've done so much sed & awk in my life I'm probably too desensitized ;-) |
So my localhost where I would run kubeadm from ansible is a mac. |
@scheuk thanks for clarifications. So, to summarize whole picture (to see, if I comprehend your setup completely):
Is that correct ? if that is correct above, can you share one more output of |
@scheuk you can try patch from #69578 to see, if it works in your setup. |
@kad your understanding of our setup is correct. Here's the output of
I'll attempt to test the patch from #69578 as well and let you know |
@kad can you send me a binary, might take less time then me setting up go/figuring how to add a patch :) |
try http://orava.kad.name/kubeadm/kubeadm-69578 |
@kad looking good:
|
good. so, please comment on PR :) |
/cc @rdodev - regarding cli-arg issue(s). |
related PR for this is in flight by @kad but reviews are pending: |
/assign @rdodev Lets chat in the morning on this one. |
In terms of cli this has already been taken care of @timothysc |
gr8! |
Just put the master's ip in place of $ (hostname -i) |
kubeadm init --apiserver-advertise-address even kubeadm join does not work. Has anyone been able to join to a cluster using --apiserver-advertise-address |
I fixed mine by not using 127.0.x.x as a try to use Example:
|
Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT
Versions
kubeadm version (use
kubeadm version
):kubeadm version: &version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:14:39Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration: Hardware
OS (e.g. from /etc/os-release):
Kernel (e.g.
uname -a
):Linux node1-lab-a1-01 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Others:
Our hosts are setup using IPv4 BGP over IPv6 (rfc5549: https://tools.ietf.org/html/rfc5549).
The host ip address is attached to a loopback address and FRR bgp announces that IP to connected TOR switches (spine and leaf fabric). There is no IPv4 address on the connected interfaces, but I do have a default route that allows access to the world:
What happened?
Having a similar problem as #982
running
Same error happens with doing
kubeadm init
What you expected to happen?
I expect kubeadm to work and pull the images or perform an init.
Maybe have a way to specify my hosts's ip address or interface.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered: