Minikube: After minikube start is completed, kubelet cannot connect to the cluster

[zhouhao3]

After minikube start is successfully executed, I cannot connect to the minkube cluster through kubelet.

Steps to reproduce the issue:

1.minikube start

# zz @ RX300 in ~ [4:14:29] 
$ minikube start 
😄  minikube v1.12.1 on Ubuntu 18.04
✨  Using the kvm2 driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating kvm2 VM (CPUs=2, Memory=4096MB, Disk=20000MB) ...
🌐  Found network options:
    ▪ http_proxy=http://127.0.0.1:8123
❗  You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP (192.168.39.111).
📘  Please see https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/ for more details
    ▪ https_proxy=http://127.0.0.1:8123
    ▪ no_proxy=http://192.168.39.215
❗  This VM is having trouble accessing https://k8s.gcr.io
💡  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.12 ...
    ▪ env HTTP_PROXY=http://127.0.0.1:8123
    ▪ env HTTPS_PROXY=http://127.0.0.1:8123
    ▪ env NO_PROXY=http://192.168.39.215
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"

1. kubectl get po -A

$ kubectl get po -A
Unable to connect to the server: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

$ minikube status      
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

[lingsamuel]

Add 192.168.0.0/16 to your NO_PROXY env variable?

[zhouhao3]

@lingsamuel Thank you for your suggestion, it solved my problem.

[lingsamuel]

The clue is in the log:

❗ You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP (192.168.39.111).

Read the log carefully can solved many problems.