Change:
BUG REPORT: (I think?) What happened: I ran the following steps on Ubuntu 16.04: Upon doing this, I receive: I've tried uninstalling , and a couple of times (even with ) and no matter what I do, it (kubeadm 1.7) doesn't generate a working . However, I run the following: and get: What you expected to happen: After initializing the master via , I expected to be able to use to install a network plugin; since it 's, I cannot do that. Environment: Kubernetes version (use ): 1.7 OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS Kernel (e.g. ): Linux radium-control 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux
There are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list
/sig cluster-lifecycle
Unsure if this helps, but I had the same and realised I was using the old setup guide, copying into and setting . I cleared the environment variable and defaults back to using .
I'm also seeing this using kubeadm v1.7 - it's preventing nodes from joining the cluster
Same error for my installation. Try with v1.6.5 and 1.6.7 it works fine.
Same problem here. . ( seems okay) ( seems okay, too) (but fails)
do you have pointing to ?
After I set the to , now it gives me a timeout error. And now I want where the came from because there is no such statement in the I'm referencing.
From the output of the node join command:
Encountered same problem while playing with kubeadm. After and for a few times, kubelet will fail communicating with apiserver because (in kubelet logs). And also blocks for ever. After removing manually, all things come back. Maybe there are problems of cleaning certificates when running ?
/area kubeadm
I am on kubeadm 1.8 and this problem still occurs. I manually checked . It was cleaned when I ran . Not sure what the actual problem is.
ATTENTION: "To start using your cluster, you need to run (as a regular user)" [root ~]# kubectl get nodes Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes") [root ~]# su - regularuser [regularuser ~] [regularuser ~] regularuser ~: [regular_user ~]$ kubectl get nodes NAME STATUS ROLES AGE VERSION NotReady master 6m v1.8.1 NotReady <none4m v1.8.1
Thanks. It works.
Please update docs with this workaround
If you kubeadm reset and then kubeadm init again, and if you ever ran the following as root, you need to run it again (as root) to get the new config: mkdir -p $ sudo cp -i $ sudo chown (id -g) $ Then you can still run as root.
if found that if you were ever going to run "sudo kubeadm reset" you'll need to remove your .kube dir to clear the cached dirs. After that you can follow oh, be sure to set KUBECONFIG to whatever you (re)name your config file to e.g. $
tanks freind ints true.
Config as the following lines, $kubectl get nodes works:
this is likely because you have a multi master setup and have generated the on each of the masters. Rather than copying them from the first master to the rest.
I found the solution in the kubernetes documentation while following the documentation dont forgot to create .kube directory using this command Because as you need this command it will move the .kube directory
For others that might have this issue, might want to try and move the folder to backup location if it exists and retry. Very possible to have a cached root version being used that is no longer valid, as you will run kubeadm as sudo.
My problem was I had custom certificates I had created during the KubeEdge Getting Started guide. Not messing around with ssl and kubeedge made it work.
export KUBECONFIG=$
that works for me , thanks a lot.
export kubectl get nodes is work from me
This worked!
After you have to remove $ folder and create new: mkdir -p $ sudo cp -i $ sudo chown (id -g) $
it worked! thx

Discussion:
fmt.Println("[reset] docker doesn't seem to be running, skipping the removal of running kubernetes containers") } <del> dirsToClean := []string{"/var/lib/kubelet", "/etc/cni/net.d", "/var/lib/dockershim"} </del> <ins> dirsToClean := []string{"/var/lib/kubelet", "/etc/cni/net.d", "/var/lib/dockershim", "/var/run/kubernetes"} </ins> // Only clear etcd data when the etcd manifest is found. In case it is not found, we must assume that the user // provided external etcd endpoints. In that case, it is his own responsibility to reset etcd