Kubernetes常见错误有哪些，能否详细列举一下？

1、屏幕持续打印Pod日志报error: unexpected EOF错误 Kubernetes: requesting flag for "kubectl logs" to avoid 5-minute timeout if no stdout/stderr When runningkubectl logs --followon a pod, after 5 minutes of no stdout/stderr, we received: $ kubectl --kubeconfig=config --namespace=foo logs --follow foo-oneoff-w8npn --container bar ###################################### # # # /system_tests/test_derp.py (1/4) # # # ###################################### RESULTS: [/system_tests/test_derp/TestDerp] Ran 4 tests in 130.044 s, ALL TESTS PASSED ###################################### # # # /system_tests/test_fuzz.py (2/4) # # # ###################################### error: unexpected EOF 解决方案： For posterity, the problem here is that we're using haproxy to serve a VIP to balance HA Kubernetes masters. Specifically we're using HA-Proxy v1.4.21, and we have this in our haproxy cfg: defaults timeout client 500000 timeout server 500000 2、K8s集群初始化成功后，kubectl get nodes 查看节点信息时报错 报错信息：The connection to the server localhost:8080 was refused - did you specify the right host or port? 解决方法： mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config 3、master节点的calico组件是0/1 Running状态，其他worker节点的calico组件是1/1 Running状态，describe pod发现是 Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with 10.244.0.1,10.244.2.12020-04-13 06:29:59.582 [INFO][682] health.go 156: Number of node(s) with BGP peering established = 0 解决办法： 修改的calico.yaml，新增两行： - name: IP_AUTODETECTION_METHOD value: "interface=eth0" value指向从ip a看到的实际网卡名。