CrashLoopBackOff、Reason: Get dial tcp i/o timeout

created at 12-11-2021 views: 21


view logs

  1. Logs view the specific error reason, and found that the reason is dial tcp i/o timeout
  2. I see that the reason is that the working node of dashboard cannot connect to API Server and the pod of master's api server works normally


① My problem is that when using kubeadm to initialize the cluster, pod-network-cidr is not specified. In this case, it is not ensured that the IP of the host/main network is in the referenced subnet.

That is, if your network is running at 192.168.., use If your network is 10.0.., use

In other words, when using the kubeadm init command to initialize the master node, when assigning the CIDR network segment to the network plug-in, the ip address in your environment (master node and working node) cannot coincide with the network plug-in network segment! (As stated on the official website)


  1. Reset the created k8s cluster (master, node)
  2. Initialize the cluster master, specify the CIDR of the pod network, and join the node node
  3. The master downloads kubernetes-dashboard.yaml and deploys access
# kubeadm reset
# kubeadm init --apiserver-advertise-address  --pod-network-cidr=
# …………
created at:12-11-2021
edited at: 12-11-2021: