minikube not getting connect from client

[amit4257]

stdout:
[init] Using Kubernetes version: v1.18.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority

stderr:
W0712 21:43:06.844098 9926 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
[WARNING DirAvailable--var-lib-minikube-etcd]: /var/lib/minikube/etcd is not empty
error execution phase certs/apiserver: failed to write or validate certificate "apiserver": failure loading apiserver certificate: failed to load certificate: the certificate has expired
To see the stack trace of this error execute with --v=5 or higher

• minikube is exiting due to an error. If the above message is not useful, open an issue:
  • https://github.com/kubernetes/minikube/issues/new/choose

[amit4257]

kindly help!!

[RA489]

/kind support

[sharifelgamal]

So it looks like the apiserver certificate has expired. This can happen when there's a very long running minikube cluster. This easiest way to workaround this is to delete and restart your cluster, as we currently don't have a way to refresh or cycle our certs automatically. Recreating the cluster will recreate the cerfs as well.

[spowelljr]

This should be fixed with #12534 which will be included in the future v1.24.0 release of minikube at the end of October.