-
Notifications
You must be signed in to change notification settings - Fork 716
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
Panic when joining a node with config and control plane #1324
Comments
@anitgandhi thank you for filing this bug report! The actual mechanics of the crash are the following. /kind bug |
/cc |
Sure, PR incoming within the next few hours. This is my first contribution so I'm just going to do a quick read of the contributing guide before I send it in 👍 |
@anitgandhi thanks! |
On a slightly tangential note, @rosti based on what you described above, if I'm going to be using a JoinConfiguration file for new master nodes, should I be including a Based on this (https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta1#JoinControlPlane) it only has |
in that case the ControlPlaneEndpoint on the root control plane node config should be sufficient for your needs. |
cherry picked here: |
@anitgandhi Having |
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/amd64"}
Note: I also observed this after building from source on
master
branch.Environment:
kubectl version
): v1.13.x and v1.14.x so faruname -a
): 4.xWhat happened?
What you expected to happen?
kubeadm
continues with the rest of its logic instead of panic'ingHow to reproduce it (as minimally and precisely as possible)?
kubeadm join --config=<path to config file> --experimental-control-plane
Anything else we need to know?
This is happening on this line, and I fixed it locally by changing the nil-check to
if internalCfg.ControlPlane != nil
. If this is the proper fix, I can submit the PR for it. I don't believe this code was present prior to v1.13.x since it's related to the new control plane join functionality.The text was updated successfully, but these errors were encountered: