-
Notifications
You must be signed in to change notification settings - Fork 715
How to debug hanging "Created API client, waiting for the control plane to become ready" #103
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
Comments
I'm mostly just opening another shell and running Do you have a proposal of what should be included? |
Thanks, I managed to get by the "waiting for the control plane to become ready", the standard debug options you suggested was enough. |
run kubelet's cgroup driver is not same with docker's cgroup driver, so I update systemd -> cgroupfs.
restart kubelet everyting is ok |
@heartarea Appreciate your steps. They work well. Also, we need to apply this changes to other nodes other than master so that they are able to join the cluster. Is this a bug? Why it is not being set as you suggested? |
I wonder if there is a way I can debug and see where in "waiting for the control plane to become ready" Kubeadm init hangs. Any -verbose parameters for kubeadm? Some other log-files or recommended debug options?
I am running Ubuntu 16.04 - but I am trying to run kubeadm from within a docker container. On my host it is working.
The text was updated successfully, but these errors were encountered: