K8S 巨坑之 nodes/集群内部无法访问ClusterIp

最新推荐文章于 2026-06-15 12:33:04 发布

原创

最新推荐文章于 2026-06-15 12:33:04 发布 · 1.2w 阅读

标签

#kubernetes

[root@master yaml]# kubectl get svc,pods -o wide
NAME                    TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                          AGE    SELECTOR
service/db              NodePort       10.105.233.179   <none>        3306:31306/TCP                   12m    io.kompose.service=db
service/webserver-tcp   NodePort       10.98.187.153    <none>        8888:30080/TCP,10443:30443/TCP   13m    app=web-server

在worker1不但pod里面无法访问mysql(上例中的db)CLUSTER-IP，在node上ping 都不通。

[root@worker1 vagrant]# ping 10.111.182.38
PING 10.111.182.38 (10.111.182.38) 56(84) bytes of data.
^C
--- 10.111.182.38 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

默认情况下，我们部署的kube-proxy通过查看日志，能看到如下信息：Flag proxy-mode="" unknown，assuming iptables proxy

[root@master vagrant]# kubectl get pod -n kube-system
NAME                                         READY   STATUS    RESTARTS   AGE
coredns-58cc8c89f4-9b548                     1/1     Running   8          4d
coredns-58cc8c89f4-g59jz                     1/1     Running   3          4d
etcd-master.localdomain                      1/1     Running   8          4d
kube-apiserver-master.localdomain            1/1     Running   8          4d
kube-controller-manager-master.localdomain   1/1     Running   8          4d
kube-flannel-ds-ck228                        1/1     Running   3          4d
kube-flannel-ds-cxb7k                        1/1     Running   3          4d
kube-flannel-ds-jf9l6                        1/1     Running   8          4d
kube-proxy-hv5q4                             1/1     Running   0          3h15m
kube-proxy-xfww6                             1/1     Running   0          3h15m
kube-proxy-xmjc2                             1/1     Running   0          3h15m
kube-scheduler-master.localdomain            1/1     Running   8          4d

发现worker1上的错误：

[root@master vagrant]# kubectl logs kube-proxy-xmjc2 -n kube-system
W0128 06:01:38.386276       1 proxier.go:597] Failed to load kernel module ip_vs with modprobe. You can ignore this