【发布时间】：2021-11-18 17:44:00
【问题描述】：
最近我通过 Terraform 创建了私有 AKS，一切正常，同一个命名空间中的两个 pod 怎么可能无法相互通信？
AKS 版本= 1.19.11 coredns:1.6.6
# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 5d18h
已使用以下资源创建集群：
Network type (plugin)=Kubenet
Pod CIDR=10.x.x.x/16
Service CIDR=10.x.x.0/16
DNS service IP=10.x.x.10
Docker bridge CIDR=172.x.x.1/16
Network Policy=Calico
Ping 响应：
/ # ping 10.x.x.89
PING 10.x.x.89 (10.x.x.89): 56 data bytes
^C
--- 10.x.x.89 ping statistics ---
25 packets transmitted, 0 packets received, 100% packet loss
/ # ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: seq=0 ttl=241 time=27.840 ms
64 bytes from 10.0.0.1: seq=1 ttl=241 time=28.790 ms
64 bytes from 10.0.0.1: seq=2 ttl=241 time=28.725 ms
^C
--- 10.0.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 27.840/28.451/28.790 ms
/ # ping kubernetes
ping: bad address 'kubernetes'
/ # nslookup kubernetes
nslookup: can't resolve '(null)': Name does not resolve
nslookup: can't resolve 'kubernetes': Name does not resolve
/ #
【问题讨论】：
-
您能否检查一下流量是否仅在同一节点上的 Pod 之间受到影响（如果是，是否有特定节点受到影响？）或仅在不同节点上的 Pod 之间或在任意两个 Pod 之间，无论它们被安排在哪个节点上？这也应该提示从您的 pod 到 coredns pod 的流量。
-
您是否已经添加了网络策略？如果有，那是什么？
标签： kubernetes containers azure-aks coredns calico