docker - Kube-DNS不起作用-6ren

docker - Kube-DNS不起作用

转载作者：行者123 更新时间：2023-12-02 21:25:27

我通过docker-multinode设置了k8s

$ https_proxy=http://10.25.30.127:7777 IP_ADDRESS=10.25.24.116 MASTER_IP=10.25.30.127 ./worker.sh
+++ [0828 15:38:35] K8S_VERSION is set to: v1.3.6
+++ [0828 15:38:35] ETCD_VERSION is set to: 3.0.4
+++ [0828 15:38:35] FLANNEL_VERSION is set to: v0.6.1
+++ [0828 15:38:35] FLANNEL_IPMASQ is set to: true
+++ [0828 15:38:35] FLANNEL_NETWORK is set to: 10.1.0.0/16
+++ [0828 15:38:35] FLANNEL_BACKEND is set to: udp
+++ [0828 15:38:35] RESTART_POLICY is set to: unless-stopped
+++ [0828 15:38:35] MASTER_IP is set to: 10.25.30.127
+++ [0828 15:38:35] ARCH is set to: amd64
+++ [0828 15:38:35] IP_ADDRESS is set to: 10.25.24.116
+++ [0828 15:38:35] USE_CNI is set to: false
+++ [0828 15:38:35] --------------------------------------------
+++ [0828 15:38:35] Killing all kubernetes containers...
+++ [0828 15:38:35] Launching docker bootstrap...
+++ [0828 15:38:36] Launching flannel...
b70f4cc14aac8315740a916fae459d0b354280d97d8da743c67e9e692beea601
+++ [0828 15:38:37] FLANNEL_SUBNET is set to: 10.1.102.1/24
+++ [0828 15:38:37] FLANNEL_MTU is set to: 1472

$ k cluster-info
Kubernetes master is running at http://10.25.30.127:8080
KubeDNS is running at http://10.25.30.127:8080/api/v1/proxy/namespaces/kube-system/services/kube-dns
kubernetes-dashboard is running at http://10.25.30.127:8080/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard

$ k get nodes
NAME              STATUS    AGE
10.25.17.232      Ready     9h
10.25.19.197      Ready     3h
10.25.24.116      Ready     7h
139.1.1.1   Ready     9h

DNS已正确启动

$ k logs kube-dns-v17.1-qaygj -c kubedns --namespace=kube-system |head -50
I0828 04:49:14.079474       1 server.go:91] Using https://10.0.0.1:443 for kubernetes master
I0828 04:49:14.081339       1 server.go:92] Using kubernetes API <nil>
I0828 04:49:14.081923       1 server.go:132] Starting SkyDNS server. Listening on port:10053
I0828 04:49:14.082071       1 server.go:139] skydns: metrics enabled on :/metrics
I0828 04:49:14.082181       1 dns.go:166] Waiting for service: default/kubernetes
I0828 04:49:14.082462       1 logs.go:41] skydns: ready for queries on cluster.local. for tcp://0.0.0.0:10053 [rcache 0]
I0828 04:49:14.082607       1 logs.go:41] skydns: ready for queries on cluster.local. for udp://0.0.0.0:10053 [rcache 0]
I0828 04:49:14.480396       1 server.go:101] Setting up Healthz Handler(/readiness, /cache) on port :8081
I0828 04:49:14.483012       1 dns.go:660] DNS Record:&{10.0.0.1 0 10 10  false 30 0  }, hash:24c3d825
I0828 04:49:14.483065       1 dns.go:660] DNS Record:&{kubernetes.default.svc.cluster.local. 443 10 10  false 30 0  }, hash:c3f6ae26
I0828 04:49:14.483115       1 dns.go:660] DNS Record:&{kubernetes.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:b9b7d845
I0828 04:49:14.483160       1 dns.go:660] DNS Record:&{10.0.0.24 0 10 10  false 30 0  }, hash:d8b58e70
I0828 04:49:14.483194       1 dns.go:660] DNS Record:&{kubernetes-dashboard.kube-system.svc.cluster.local. 0 10 10  false 30 0  }, hash:529066a8
I0828 04:49:14.483237       1 dns.go:660] DNS Record:&{10.0.0.10 0 10 10  false 30 0  }, hash:2d9aa69
I0828 04:49:14.483266       1 dns.go:660] DNS Record:&{kube-dns.kube-system.svc.cluster.local. 53 10 10  false 30 0  }, hash:fdbb4e78
I0828 04:49:14.483309       1 dns.go:660] DNS Record:&{kube-dns.kube-system.svc.cluster.local. 53 10 10  false 30 0  }, hash:fdbb4e78
I0828 04:49:14.483337       1 dns.go:660] DNS Record:&{kube-dns.kube-system.svc.cluster.local. 0 10 10  false 30 0  }, hash:d1247c4e
I0828 04:49:16.678334       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:49:16.678405       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:49:16.777991       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:49:16.778100       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:49:16.778886       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:49:46.778352       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:49:46.778406       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:49:46.778932       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:50:16.879611       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:50:16.879685       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:50:16.880274       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:50:16.880332       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:50:16.880900       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:50:46.878037       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:50:46.878094       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:50:46.978007       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:51:16.778397       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:51:16.778455       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:51:16.779062       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:51:16.779110       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:51:16.779588       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:51:46.778319       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:51:46.778374       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:51:46.779048       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:52:16.878240       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:52:16.878309       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:52:16.878848       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:52:16.878886       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:52:16.977642       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:52:46.678628       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false
I0828 04:52:46.678685       1 dns.go:539] records:[0xc820356af0], retval:[{10.0.0.1 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/3234633364383235}], path:[local cluster svc default kubernetes]
I0828 04:52:46.878096       1 dns.go:583] Received ReverseRecord Request:1.0.0.10.in-addr.arpa.
I0828 04:53:16.679056       1 dns.go:439] Received DNS Request:kubernetes.default.svc.cluster.local., exact:false

启动留言簿时，我注意到dns日志

I0828 14:39:07.977746       1 dns.go:660] DNS Record:&{redis-master.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:606d0bd5
I0828 14:39:14.178122       1 dns.go:660] DNS Record:&{10.0.0.147 0 10 10  false 30 0  }, hash:e8b710be
I0828 14:39:14.178212       1 dns.go:660] DNS Record:&{myapp.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:2077e618
I0828 14:39:14.178254       1 dns.go:660] DNS Record:&{10.0.0.145 0 10 10  false 30 0  }, hash:d93e9f2c
I0828 14:39:14.178296       1 dns.go:660] DNS Record:&{redis-master.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:606d0bd5
I0828 14:39:14.178336       1 dns.go:660] DNS Record:&{10.0.0.171 0 10 10  false 30 0  }, hash:cb7a4915
I0828 14:39:14.178364       1 dns.go:660] DNS Record:&{redis-slave.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:ff7d45d8
I0828 14:39:14.178404       1 dns.go:660] DNS Record:&{10.0.0.139 0 10 10  false 30 0  }, hash:9afc24c9
I0828 14:39:14.178431       1 dns.go:660] DNS Record:&{guestbook.default.svc.cluster.local. 0 10 10  false 30 0  }, hash:78248924
I0828 14:39:14.178456       1 dns.go:660] DNS Record:&{10.0.0.1 0 10 10  false 30 0  }, hash:24c3d825
I0828 14:39:14.178513       1 dns.go:660] DNS Record:&{kubernetes.default.svc.cluster.local. 443 10 10  false 30 0  }, hash:c3f6ae26

但是DNS查找不起作用

留言簿信息报告

PANIC: dial tcp: lookup redis-master on 10.0.0.10:53: read udp 10.1.102.2:46755->10.0.0.10:53: i/o timeout
goroutine 277 [running]:
github.com/codegangsta/negroni.(*Recovery).ServeHTTP.func1(0x7f1d98e5ba90, 0xc820323580, 0xc8200b8ec0)
    /go/src/github.com/codegangsta/negroni/recovery.go:34 +0xe9
panic(0x7a8c60, 0xc820327ae0)

访客留言页

{
  "GUESTBOOK_PORT": "tcp://10.0.0.139:3000",
  "GUESTBOOK_PORT_3000_TCP": "tcp://10.0.0.139:3000",
  "GUESTBOOK_PORT_3000_TCP_ADDR": "10.0.0.139",
  "GUESTBOOK_PORT_3000_TCP_PORT": "3000",
  "GUESTBOOK_PORT_3000_TCP_PROTO": "tcp",
  "GUESTBOOK_SERVICE_HOST": "10.0.0.139",
  "GUESTBOOK_SERVICE_PORT": "3000",
  "HOME": "/",
  "HOSTNAME": "guestbook-advba",
  "KUBERNETES_PORT": "tcp://10.0.0.1:443",
  "KUBERNETES_PORT_443_TCP": "tcp://10.0.0.1:443",
  "KUBERNETES_PORT_443_TCP_ADDR": "10.0.0.1",
  "KUBERNETES_PORT_443_TCP_PORT": "443",
  "KUBERNETES_PORT_443_TCP_PROTO": "tcp",
  "KUBERNETES_SERVICE_HOST": "10.0.0.1",
  "KUBERNETES_SERVICE_PORT": "443",
  "KUBERNETES_SERVICE_PORT_HTTPS": "443",
  "MYAPP_PORT": "tcp://10.0.0.147:8765",
  "MYAPP_PORT_8765_TCP": "tcp://10.0.0.147:8765",
  "MYAPP_PORT_8765_TCP_ADDR": "10.0.0.147",
  "MYAPP_PORT_8765_TCP_PORT": "8765",
  "MYAPP_PORT_8765_TCP_PROTO": "tcp",
  "MYAPP_SERVICE_HOST": "10.0.0.147",
  "MYAPP_SERVICE_PORT": "8765",
  "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
  "REDIS_MASTER_PORT": "tcp://10.0.0.35:6379",
  "REDIS_MASTER_PORT_6379_TCP": "tcp://10.0.0.35:6379",
  "REDIS_MASTER_PORT_6379_TCP_ADDR": "10.0.0.35",
  "REDIS_MASTER_PORT_6379_TCP_PORT": "6379",
  "REDIS_MASTER_PORT_6379_TCP_PROTO": "tcp",
  "REDIS_MASTER_SERVICE_HOST": "10.0.0.35",
  "REDIS_MASTER_SERVICE_PORT": "6379",
  "REDIS_SLAVE_PORT": "tcp://10.0.0.171:6379",
  "REDIS_SLAVE_PORT_6379_TCP": "tcp://10.0.0.171:6379",
  "REDIS_SLAVE_PORT_6379_TCP_ADDR": "10.0.0.171",
  "REDIS_SLAVE_PORT_6379_TCP_PORT": "6379",
  "REDIS_SLAVE_PORT_6379_TCP_PROTO": "tcp",
  "REDIS_SLAVE_SERVICE_HOST": "10.0.0.171",
  "REDIS_SLAVE_SERVICE_PORT": "6379"
}

我也尝试在dns pod中解决

$ k get svc --namespace=kube-system
NAME                   CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
kube-dns               10.0.0.10    <none>        53/UDP,53/TCP   10h
kubernetes-dashboard   10.0.0.24    <none>        80/TCP          10h
$ k exec -it kube-dns-v17.1-qaygj -c kubedns --namespace=kube-system -- /bin/sh
/ # nslookup redis-master
Server:    10.143.22.118
Address 1: 10.143.22.118

nslookup: can't resolve 'redis-master'
/ # nslookup baidu.com
Server:    10.143.22.118
Address 1: 10.143.22.118

Name:      baidu.com
Address 1: 111.13.101.208
Address 2: 220.181.57.217
Address 3: 123.125.114.144
Address 4: 180.149.132.47
/ # nslookup redis-master 10.0.0.10
Server:    10.0.0.10
Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local

nslookup: can't resolve 'redis-master'
/ # nslookup baidu.com 10.0.0.10
Server:    10.0.0.10
Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local

Name:      baidu.com
Address 1: 123.125.114.144
Address 2: 180.149.132.47
Address 3: 111.13.101.208
Address 4: 220.181.57.217

为什么kube-dns不起作用？

最佳答案

此问题是由ip冲突引起的，提供程序使用10作为内部网络，docker-multinode使用10/8作为默认群集ip范围，然后进行了连接。

这就是我所做的

在容器

外部复制/ etc / kubernetes

将10.0.0.1替换为172.16.0.1中的/etc/kubernetes/master-multi/master-multi.json

将addon中的/etc/kubernetes/master-multi/addon-manager.json音量更改为

{
“name”:“addons”，
“hostPath”:{“路径”:“/路径/到/您/自己/ etc / kubernetes /”}

将clusterIP中的/etc/kubernetes/addon/skydns-svc.yaml更改为172.16.0.10

将--cluster-dns=10.0.0.10中的所有common.sh更改为--cluster-dns=172.16.0.10

将-v /path/to/you/own/etc/kubernetes/:/etc/kubernetes/ \添加到common.sh中的KUBECTL_MOUNT

然后FLANNEL_IPMASQ=false FLANNEL_NETWORK=172.16.0.0/16 ./master.sh

完成

我还向kube-deploy kube-deploy#215添加了一个问题

关于docker - Kube-DNS不起作用，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/39192572/

文章推荐： docker - 启动运行docker镜像时如何设置运行bash文件

文章推荐： hadoop - 找不到我的数据写在HDFS与水槽

文章推荐： hadoop - 如何将数据从Hortonworks配置单元导出到Cassandra？

docker - docker ， docker 没有IPAddress检查
我正在使用以下dockerfile: FROM ubuntu:14.04 MAINTAINER xxx xxx # SSH RUN apt-get update && apt-get install
docker - Docker docker-compose不获取相关的缓存镜像
我运行了docker-compose build celery，(经过数小时的尝试，我的连接不良)成功了。 app Dockerfile的前80％是相同的，但不会重复使用缓存。从我可以浏览的内容来看，
docker - docker 守护进程重新启动后，Docker 注册表中的所有存储库都会被删除 (docker-for-mac)
我可以使用以下命令成功创建 Docker 注册表 v2 服务:docker service create 然后我使用 docker Push 将一些图像推送到该服务。当我通过 curl localh
docker - 无法连接到 docker 的 docker 镜像中的守护进程 docker
我正在尝试使用 gitlab 构建 CI，我从 docker 的 docker 镜像开始，我的前端存储库没有任何问题，但现在使用相同的 gitlab-ci 配置文件，我有此守护程序错误。这是构建的输
docker - 最小化 Docker-in-Docker 容器内的 `docker build` 执行时间
用例: 我们在 Jenkins 中有几个“发布作业”build 和 push 应用程序的 Docker 镜像到 docker registry，更新各种文件中的项目版本，最后将发布标签推送到相应的 G
docker - 我无法使用 Docker 构建我的 docker 文件来创建我的 docker 镜像
当我尝试构建我的 docker 文件时，docker 返回以下错误: [+] Building 0.0s (1/2)
docker - 如何在不使用 docker-in-docker 的情况下在 jenkins 管道中使用 docker
docker-in-docker 的作者在此博客中建议不要将此图像用于 CI 目的: jpetazzo/Using Docker-in-Docker for your CI or testing en
docker - 在 Docker 容器中运行 Docker : Cannot connect to the Docker daemon
我创建了一个 Dockerfile 来在 Docker 中运行 Docker: FROM ubuntu:16.04 RUN apt-get update && \ apt-get in
docker - 如何在 Docker 命令行的 Docker 注册表中找到具有特定标记的 Docker 镜像？
我尝试为 Docker 镜像定位一个特定标签。我怎样才能在命令行上做到这一点？我想避免下载所有图像，然后删除不需要的图像。在 Ubuntu 官方版本中，https://registry.hub.do
docker - docker 内的 docker ，发布HTTP错误
我正在尝试在docker中运行docker。唯一的目的是实验性的，我绝不尝试实现任何功能，我只想检查docker从另一个docker运行时的性能。我通过Mac上的boot2docker启动docke
docker - Docker:docker-compose.yml中用于自动重新部署新镜像的选项
docker-compose.yml version: "3" services: daggr: image: "docker.pvt.com/test/daggr:stable"
docker - 在 Docker 容器内访问 Docker
我有一个非常具体的开发环境用例。在一些代码中，我启动了一个容器来抓取页面并检索在容器中运行的服务(Gitlab)的 token 。现在，我希望 Dockerize 运行它的代码。具体来说，类似: o
docker - docker-compose文件vs docker bundle
之前已经问过这个问题，但我不确定当时是否可以使用docker-compose文件完成docker堆栈部署。由于最新版本支持使用compose将服务部署到堆栈，因此，我无法理解dab文件的值。我检查
docker - docker 池和 docker 注册表有什么区别？
我在一次采访中被问到这个问题，但无法回答。也没有找到任何相关信息。最佳答案正如 Docker 文档中所述，Docker 注册表是: [...] a hosted service containin
docker - docker :如何将 docker 中的所有png文件复制到主机？
有没有一种方法可以将具有给定扩展名的所有文件复制到Docker中的主机？就像是 docker cp container_name:path/to/file/in/docker/*.png path/o
docker - docker 日志级别会影响日志记录驱动程序还是仅影响 docker 守护程序的日志？
我的日志驱动程序设置为journald。使用日志记录驱动程序时，daemon.json文件中的日志级别配置会影响日志吗？使用docker logs 时仅会影响容器日志？例如，docker和journ
docker - docker 服务如何管理从单独的 docker 容器调用实例？
我最近开始使用Docker + Celery。我还共享了full sample codes for this example on github，以下是其中的一些代码段，以帮助解释我的观点。就上下文
docker - docker :无法提交构建的 docker 镜像
运行docker build .命令后，尝试提交构建的镜像，但收到以下错误 Step 12 : CMD activator run ---> Using cache ---> efc82ff1ca
docker - Docker + docker-组成+无法启动服务
我们有docker-compose.yml，其中包含Kafka，zookeeper和schema registry的配置当我们启动docker compose时，出现以下错误 docker-comp
docker - docker 基本图像存储库ouside docker 中心？
我是Docker的新手。是否可以在Docker Hub外部建立Docker基本镜像存储库？假设将它们存储在您的云中，而不是拥有DH帐户？谢谢。最佳答案您可以根据需要托管自己的注册表。可以在Depl

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

docker - Kube-DNS不起作用