【发布时间】:2019-07-02 02:57:04
【问题描述】:
我在从外部 default 命名空间解析 kubernetes.default.svc.cluster.local 时遇到问题
我在每个命名空间上运行两个 busybox:1.30 pod,并且名称仅从 default 命名空间成功解析
[admin@devsvr3 ~]$ kubectl exec -n default -ti busybox -- nslookup kubernetes
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
Name: kubernetes
Address 1: 10.96.0.1 kubernetes.default.svc.cluster.local
[admin@devsvr3 ~]$ kubectl exec -n namespace-dev -ti busybox -- nslookup kubernetes
Server: 10.96.0.10
Address: 10.96.0.10:53
** server can't find kubernetes.namespace-dev.svc.cluster.local: NXDOMAIN
*** Can't find kubernetes.svc.cluster.local: No answer
*** Can't find kubernetes.cluster.local: No answer
*** Can't find kubernetes.namespace-dev.svc.cluster.local: No answer
*** Can't find kubernetes.svc.cluster.local: No answer
*** Can't find kubernetes.cluster.local: No answer
[admin@devsvr3 ~]$
我在气隙环境中运行 CentOS 7 kubernetes 集群并使用 weave net CNI 插件,这是我的 CoreDNS 配置
apiVersion: v1
data:
Corefile: |
.:53 {
log
errors
health
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
upstream
fallthrough in-addr.arpa ip6.arpa
}
prometheus :9153
proxy . /etc/resolv.conf
cache 30
reload
loadbalance
}
kind: ConfigMap
metadata:
creationTimestamp: "2019-01-28T10:59:25Z"
name: coredns
namespace: kube-system
resourceVersion: "1177652"
selfLink: /api/v1/namespaces/kube-system/configmaps/coredns
uid: c6b5ddae-22eb-11e9-8689-0017a4770068
【问题讨论】:
-
Weave 是拥有网络策略的 CNI 提供商之一,所以我敢打赌它与此有关:kubernetes.io/docs/tasks/administer-cluster/…(可能是
kubectl get --all-namespaces networkpolicy.networking.k8s.io)
标签: kubernetes centos weave coredns kube-apiserver