minikube: kubeadm init: failure loading apiserver certificate: the certificate is not valid yet
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version (use minikube version): minikube version: v0.26.0
- OS (e.g. from /etc/os-release): MacOS Siera 10.12
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): “Boot2DockerURL”: “file:///Users/122462/.minikube/cache/iso/minikube-v0.26.0.iso”, - Install tools: brew cask install minikube
- Others: The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver":
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json
What happened:
Executed minikube start
What you expected to happen:
minikube successfully starts
How to reproduce it (as minimally and precisely as possible):
Execute minikube start
Output of minikube logs (if applicable): (not actually minikube log, I got this when executed minikube start)
E0411 16:57:04.402812 4049 start.go:276] Error starting cluster: kubeadm init error sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap running command: : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap
output: [init] Using Kubernetes version: v1.10.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
[certificates] Using the existing ca certificate and key.
[WARNING Swap]: running with swap on is not supported. Please disable swap
Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
failure loading apiserver certificate: the certificate is not valid yet
: running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap
.: Process exited with status 1
Anything else do we need to know: VirtualBox 5.2.8
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 20
- Comments: 15 (1 by maintainers)
Commits related to this issue
- Change --skip-preflight-checks to --ignore-preflight-errors In January 2018, the parameter was changed. See: https://github.com/kubernetes/minikube/issues/2703 Removes the error caused by: ``` ... — committed to cdrage/kubeadm-ansible by cdrage 6 years ago
- Change --skip-preflight-checks to --ignore-preflight-errors In January 2018, the parameter was changed. See: https://github.com/kubernetes/minikube/issues/2703 Removes the error caused by: ``` ... — committed to cdrage/kubeadm-ansible by cdrage 6 years ago
I’ve got this here too.
I even tried
minikube deleteandminikube startand from fresh this issue still raises its head.After running
minikube logs, this line caught my eye.minikube kubelet[3329]: error: failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directoryI’m not sure if this has significance or not
edit: Boom. Here we go:
Since Minikube version 0.26.0 I am getting this error too with “minikube start” on Windows 10 + VirtualBox 5.2.8 (latest). I have been sticking with 0.25.2.
Related to this report I captured my details in issue #2818.
I’ll get same issue here:
output: [init] Using Kubernetes version: v1.10.0 [init] Using Authorization modes: [Node RBAC] [preflight] Running pre-flight checks. [certificates] Using the existing ca certificate and key. [WARNING Swap]: running with swap on is not supported. Please disable swap Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version. failure loading apiserver certificate: the certificate is not valid yet : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI .: Process exited with status 1Go back to 0.25.1 works for me.
Mac OS 1.12.6
Minikube 0.26.0 cluster initialization still failing. My dependency is on k8s-v1.10 cluster.
How soon can we expect new version release with few important fixes like #2721
Is anyone able to run Kubernetes cluster 1.10 with Minikube 0.26.0 ?
Still the same error on 0.27, Win 8.1 and Vbox 5.1; Going back to 0.25.2 as that’s the last known good version for me.
Why is minikube upgrade always so error prone 😦… Thankfully, its easy to create a new profile and test with that rather than muck with an existing working installation.
as workaround - I started minikube from this release https://github.com/kubernetes/minikube/releases/tag/v0.25.1 At least works on hight sierra 10.13.3
+1
I also got the same
unknown flag: --ignore-preflight-errorserror when trying to start a k8s v1.8 cluster with minikube 0.26.I was able to work around it temporarily by downgrading to minikube 0.25.2, thanks for the tip @mrballcb!