无法在Kubernetes中到达绑定dns

问题描述 投票:0回答:1

我正在尝试使用microK8S在本地Kubernetes群集中安装DNS服务器,但无法访问DNS。

这里部署脚本:

---
kind: Deployment
apiVersion: apps/v1
metadata:
  name: bind
  labels:
    app: bind
spec:
  replicas: 1
  selector:
    matchLabels:
      app: bind
  template:
    metadata:
      labels:
        app: bind
    spec:
      containers:
        - name: bind
          image: sameersbn/bind
          env:
            - name: ROOT_PASSWORD
              value: "toto"
          volumeMounts:
            - mountPath: /data
              name: data
          ports:
            - containerPort: 53
              protocol: UDP
            - containerPort: 53
              protocol: TCP
            - containerPort: 10000
      volumes:
        - name: data
          emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
  name: bind-dns
  labels:
    name: bind-dns
spec:
  type: ClusterIP
  ports:
    - name: dns
      port: 53
      targetPort: 53
      protocol: UDP
    - name: dns-tcp
      port: 53
      protocol: TCP
      targetPort: 53
  selector:
    name: bind

服务通过ip公开

bind-dns        LoadBalancer   10.152.183.144   <pending>     53/UDP,53/TCP     11m

当我用SSH绑定到绑定pod时有效

host www.google.com 0.0.0.0
Using domain server:
Name: 0.0.0.0
Address: 0.0.0.0#53
Aliases: 

www.google.com has address 172.217.13.132
www.google.com has IPv6 address 2607:f8b0:4020:805::2004

但是在外部容器中却没有

host www.google.com 10.152.183.144
;; connection timed out; no servers could be reached

怎么了?为什么我无法访问服务器?

kubernetes dns bind microk8s
1个回答
0
投票

服务资源spec.selector需要指定广告连播spec.metadata.labels。因此,我认为您需要更改yaml文件的服务资源。

apiVersion: v1
kind: Service
metadata:
  name: bind-dns
  labels:
    name: bind-dns
spec:
  type: ClusterIP
  ports:
    - name: dns
      port: 53
      targetPort: 53
      protocol: UDP
    - name: dns-tcp
      port: 53
      protocol: TCP
      targetPort: 53
  selector:
    app: bind # changed
© www.soinside.com 2019 - 2024. All rights reserved.