kubeadm: [apiclient] Created API client, waiting for the control plane to become ready stuck
Is this a request for help?
If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.
What keywords did you search in kubeadm issues before filing this one?
[apiclient] Created API client, waiting for the control plane to become ready stuck, I search through all open /close issues on this subject but I couldnt find on running cluster on 1.7.4 version.
If you have found any duplicates, you should instead reply there and close this page.
If you have not found any duplicates, delete this section and continue on.
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version (use kubeadm version):
kubeadm version: &version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.3”, GitCommit:“2c2fe6e8278a5db2d15a013987b53968c743f2a1”, GitTreeState:“clean”, BuildDate:“2017-08-03T06:43:48Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”}
Environment:
-
Kubernetes version (use
kubectl version): Client Version: version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.3”, GitCommit:“2c2fe6e8278a5db2d15a013987b53968c743f2a1”, GitTreeState:“clean”, BuildDate:“2017-08-03T07:00:21Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”} The connection to the server localhost:8080 was refused - did you specify the right host or port? -
Cloud provider or hardware configuration:
-
OS (e.g. from /etc/os-release): kubeadm version: &version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.3”, GitCommit:“2c2fe6e8278a5db2d15a013987b53968c743f2a1”, GitTreeState:“clean”, BuildDate:“2017-08-03T06:43:48Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”} [root@node01 ~]# kubectl version Client Version: version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.3”, GitCommit:“2c2fe6e8278a5db2d15a013987b53968c743f2a1”, GitTreeState:“clean”, BuildDate:“2017-08-03T07:00:21Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”} The connection to the server localhost:8080 was refused - did you specify the right host or port? [root@node01 ~]# more /etc/os-release NAME=“CentOS Linux” VERSION=“7 (Core)” ID=“centos” ID_LIKE=“rhel fedora” VERSION_ID=“7” PRETTY_NAME=“CentOS Linux 7 (Core)” ANSI_COLOR=“0;31” CPE_NAME=“cpe:/o:centos:centos:7” HOME_URL=“https://www.centos.org/” BUG_REPORT_URL=“https://bugs.centos.org/”
CENTOS_MANTISBT_PROJECT=“CentOS-7” CENTOS_MANTISBT_PROJECT_VERSION=“7” REDHAT_SUPPORT_PRODUCT=“centos” REDHAT_SUPPORT_PRODUCT_VERSION=“7”
- Kernel (e.g.
uname -a): Linux node01 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux - Others:
What happened?
when I am running kubeadm init the process stuck at [apiclient] Created API client, waiting for the control plane to become ready
What you expected to happen?
I would like my kubeadm init to initialize the ready as per documentation on below link https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/
How to reproduce it (as minimally and precisely as possible)?
I am following the instruction as per and setup kubeadm, kubectl and updated but having issues https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/
Anything else we need to know?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 17 (2 by maintainers)
@selvik
Notice presence of “-unstable”.
Others, sorry for responding with Ubuntu specific steps on a CentOS related thread.
Update on my issue: It was indeed a proxy issue, if anyone else was having the same scenario as myself:
If your kubeadm init is hanging but when you run docker ps and the containers are running. Check to see that you can access your apiserver at localhost:6443 if so, try at
<public ip>:6443.If the public ip fails, check the logs of your controller-manager by doing docker logs
<id of controller-manager>. You should see that all the api requests are to your public ip and they are failing.In my case, this was a proxy problem because when I tried to curl my apiserver at
<public ip>:6443, I’d get a 403 from proxy after connect error.How I fixed it: Basically the controller-manager container has to have its NO_PROXY/no_proxy env var to include your public ip. From a previous project, I had to set some HTTP and HTTPS_PROXY env vars in my docker daemon and I had overlooked them, now I had to add NO_PROXY env variable for my docker daemon by going to /etc/systemd/system/docker.service.d and creating a file http-proxy.conf in there. Then I put
[Service] <MY PREVIOUS HTTP AND HTTPS PROXY SETTINGS> Environment="NO_PROXY=localhost,127.0.0.1,<YOUR PUBLIC IP>"then do systemctl daemon-reload, and systemctl restart docker. Do docker info and look at No Proxy to confirm that your machine’s ip shows up there. Then stop kubeadm init if you still had it running, do kubeadm reset, then do kubeadm init again. Hopefully it works!
BTW: I’m not the best at configuring these proxy settings, if there is a better way to do this, please let me know
@ParagDoke Can you share the steps you used to install kubeadm 1.7.4? I am facing the same issue as you did. Thanks!
Thanks @jiangpengcheng. Maybe a different issue on CentOS then. For me (on Ubuntu 16.04), using the unstable package worked (I got kubeadm 1.7.4).