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

Node can't join the cluster #1326

Closed
profiluefter opened this issue Dec 18, 2018 · 1 comment
Closed

Node can't join the cluster #1326

profiluefter opened this issue Dec 18, 2018 · 1 comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@profiluefter
Copy link

profiluefter commented Dec 18, 2018

What keywords did you search in kubeadm issues before filing this one?

raspberry pi; invalid token; can't join

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

kubeadm version (use kubeadm version):

kubeadm version: &version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:36:44Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/arm"}

Environment:

  • Kubernetes version (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/arm"} Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:31:33Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/arm"}
  • Cloud provider or hardware configuration: 4 Raspberry Pis connected with ethernet but wlan doesn''t change it. The master has the static ip 10.0.0.1 and the nodes have 10.0.0.201 - 10.0.0.203
  • OS (e.g. from /etc/os-release): HypriotOS, but it neither works with Raspbian
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
HYPRIOT_OS="HypriotOS/armhf"
HYPRIOT_OS_VERSION="v2.0.1"
HYPRIOT_DEVICE="Raspberry Pi"
HYPRIOT_IMAGE_VERSION="v1.9.0"
  • Kernel (e.g. uname -a):
    Linux master 4.14.34-hypriotos-v7+ #1 SMP Sun Apr 22 14:57:31 UTC 2018 armv7l GNU/Linux

What happened?

After successfully executing sudo kubeadm init --pod-network-cidr=10.0.0.200/28 --apiserver-advertise-address=10.0.0.1 on the master node, I can't join the other nodes because of: Failed to connect to API Server "10.0.0.1:6443": token id "wpiklq" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token
I tried generating a new token, but that didn't change anything. Also I'm able to communicate between the nodes on the port 6443.(I tested the port with netcat)

What you expected to happen?

I expected that the node would join the cluster.

How to reproduce it (as minimally and precisely as possible)?

Download HypriotOS and flash it to a SD card.
Add the repo and install kubeadm.
Create a cluster on the master node.
Try to connect from the client.

Anything else we need to know?

Don't think so.

Edit: My issue is basically the same as #1108, but The reason was 'Controller: Invalid --cluster-cidr, mask size of cluster CIDR must be less than --node-cidr-mask-size' didn't help me that much. (Also i tried to generate a token with ttl=0)

@neolit123 neolit123 added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Dec 18, 2018
@profiluefter
Copy link
Author

Sorry, just reread the documentation and found out that --pod-network-cidr shouldn't point to the "real" IP addresses of the nodes, but rather it should be a range, where the virtual network is. And I guess that connections from the internal network shouldn't be accepted.
(Also I think it should be documented more clearly, because I only found this information in "Installing a pod network add-on" under the flannel tab.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

2 participants