restarting kube-proxy wating for conditions

While running the minikube start in windows 10, getting the following error.

Error : Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

Please help me resolve the give issue, I delete the minikube and restarted many time.

What happens if kube-proxy is down?

kube-proxy plays a kind of enforcer whereby it takes charge of checking with master, syncing the information and enforcing the rules on the list. If the master node(API server) is down, the cluster will not be able to respond to API commands or deploy nodes.

How do I check my kube-proxy status?

In order to track kube-proxy in Sysdig Monitor, you have to add some sections to the Sysdig agent YAML configuration file, and use a Prometheus server to filter the metrics. You can choose not to use an intermediate Prometheus server, but you have to keep in mind that kube-proxy provides a lot of metrics.

I faced the same issue on Centos 7

minikube delete

then

minikube start

solved my issue