pod无法通过名字相互访问

来源:8-5 cicd实践(4)

Cliven_cn

2019-08-23

果果老师,我的是通过kubeadm安装的服务,DNS 服务都是正常的

[root@YiWu ~]# kubectl get pods -n kube-system
NAME                            READY   STATUS    RESTARTS   AGE
calico-node-dp69k               2/2     Running   0          8d
calico-node-lcjq2               2/2     Running   0          8d
calico-node-zbj54               2/2     Running   0          8d
calico-typha-666749994b-fx6ps   1/1     Running   0          8d
coredns-8567978547-t6mkl        1/1     Running   0          18m
coredns-8567978547-vqdgg        1/1     Running   0          18m
etcd-yiwu                       1/1     Running   1          8d
kube-apiserver-yiwu             1/1     Running   2          8d
kube-controller-manager-yiwu    1/1     Running   2          8d
kube-proxy-7pjcx                1/1     Running   2          8d
kube-proxy-96d2j                1/1     Running   3          8d
kube-proxy-j5cnw                1/1     Running   1          8d
kube-scheduler-yiwu             1/1     Running   1          8d

DNS 服务的日志也正常

[root@YiWu ~]# kubectl logs  coredns-8567978547-t6mkl -n kube-system
.:53
2019-08-23T09:57:16.271Z [INFO] CoreDNS-1.3.1
2019-08-23T09:57:16.271Z [INFO] linux/amd64, go1.11.4, 6b56a9c
CoreDNS-1.3.1
linux/amd64, go1.11.4, 6b56a9c
2019-08-23T09:57:16.271Z [INFO] plugin/reload: Running configuration MD5 = 599b9eb76b8c147408aed6a0bbe0f669
[root@YiWu ~]# kubectl logs  coredns-8567978547-vqdgg -n kube-system
.:53
2019-08-23T09:57:28.075Z [INFO] CoreDNS-1.3.1
2019-08-23T09:57:28.075Z [INFO] linux/amd64, go1.11.4, 6b56a9c
CoreDNS-1.3.1
linux/amd64, go1.11.4, 6b56a9c
2019-08-23T09:57:28.075Z [INFO] plugin/reload: Running configuration MD5 = 599b9eb76b8c147408aed6a0bbe0f669

我启动的nginx-ds服务,然后启动了一个版本为1.28的busyboxpod,进入容器中相互ping发现无法解析dns

[root@YiWu ~]# kubectl get pods
NAME                                         READY   STATUS    RESTARTS   AGE
busybox                                      1/1     Running   2          35m
nginx-ds-2w9dc                               1/1     Running   0          36m
nginx-ds-55xpv                               1/1     Running   0          36m
nginx-ds-g6g8q                               1/1     Running   0          36m
unisign-eureka-center-0                      1/1     Running   0          104m
unisign-eureka-center-1                      1/1     Running   0          103m
unisign-service-dashborad-8656d4fd48-djc9f   1/1     Running   0          101m


[root@YiWu ~]# kubectl exec -it busybox sh
/ # ping nginx-ds-2w9dc
ping: bad address 'nginx-ds-2w9dc'
/ # ping nginx-ds-55xpv 
ping: bad address 'nginx-ds-55xpv'
/ # ping nginx-ds-g6g8q
ping: bad address 'nginx-ds-g6g8q'


/ # cat /etc/resolv.conf 
nameserver 10.96.0.10
search default.svc.cluster.local svc.cluster.local cluster.local
options ndots:5


/ #  nslookup kubernetes.default
Server:    10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local

Name:      kubernetes.default
Address 1: 10.96.0.1 kubernetes.default.svc.cluster.local

似乎是dns组件出问题,但是日志看不出来任何迹象…僵住了

写回答

1回答

刘果国

2019-08-24

亲 为什么要ping pod的名字 可以解析的只有service name啊

1
1
Cliven_cn
正如果果老师所说
2019-08-26
共1条回复

Kubernetes生产落地全程实践

一个互联网公司落地Kubernetes全过程点点滴滴

2293 学习 · 2216 问题

查看课程