-
Notifications
You must be signed in to change notification settings - Fork 5k
Closed
Labels
cause/firewall-or-proxyWhen firewalls or proxies seem to be interferingWhen firewalls or proxies seem to be interferingco/kube-proxyissues relating to kube-proxy in some wayissues relating to kube-proxy in some wayco/kubeadmIssues relating to kubeadmIssues relating to kubeadmfailed/local-networkingstartup failures due to networking issuesstartup failures due to networking issueskind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
I start minikube by minikube start command
Starting local Kubernetes v1.10.0 cluster... Starting VM... Getting VM IP address... Moving files into cluster... Setting up certs... Connecting to cluster... Setting up kubeconfig... Starting cluster components... E0420 20:42:38.971223 4270 start.go:281] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
and I get this error
how can I fix it
tsantef, claytondus, ljnelson, cmal, chriszacny and 83 moreabdennour, Skarlso, tech-mint and asteffes-mfp
Metadata
Metadata
Assignees
Labels
cause/firewall-or-proxyWhen firewalls or proxies seem to be interferingWhen firewalls or proxies seem to be interferingco/kube-proxyissues relating to kube-proxy in some wayissues relating to kube-proxy in some wayco/kubeadmIssues relating to kubeadmIssues relating to kubeadmfailed/local-networkingstartup failures due to networking issuesstartup failures due to networking issueskind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.