- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我通过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
$ 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
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
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"
}
$ 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
最佳答案
此问题是由ip冲突引起的,提供程序使用10作为内部网络,docker-multinode使用10/8作为默认群集ip范围,然后进行了连接。
这就是我所做的
10.0.0.1
替换为172.16.0.1
中的/etc/kubernetes/master-multi/master-multi.json
addon
中的/etc/kubernetes/master-multi/addon-manager.json
音量更改为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
关于docker - Kube-DNS不起作用,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/39192572/
我正在使用 rke在私有(private)云中生成 Kubernetes 集群。它产生 kube_config_cluster.yml文件。有没有办法将此配置添加到我的 $HOME/.kube/con
我尝试在我的桌面(Ubuntu 18)上运行 OKD。我按照指示:https://opensource.com/article/18/11/local-okd-cluster-linux (simil
我在我的 k8s 中使用 calico 作为 CNI,我试图在 3 个服务器中部署一个主集群。我用的是kubeadm,关注官方setup guide .但是发生了一些错误,kube-controlle
Fresh Kubernetes (1.10.0) 集群使用 kubeadm (1.10.0) 安装在 RHEL7 裸机虚拟机上 Linux 3.10.0-693.11.6.el7.x86_64 #1
我使用 kubeadm 安装了 kubernetes .为了启用基本身份验证,我添加了 --basic-auth-file=/etc/kubernetes/user-password.txt在我的 /
我尝试使用 minikube start 启动本地 Kubernetes 集群并收到以下错误。 Starting local Kubernetes v1.10.0 cluster... Startin
我用了this tutorial在我的 Raspberry 3 上设置一个 kubernetes 集群。 我按照说明进行操作,直到设置 flannel 为止: curl -sSL https://ra
我有一个本地 kubernetes 集群 v1.22.1(1 个主节点和 2 个工作节点),并且想使用 jenkins 上的 kubernetes 插件在这个 kubernetes 集群上运行 jen
我只是尝试运行一个简单的批处理作业并收到此错误“卷“kube-api-access-cvwdt”的 MountVolume.SetUp 失败:对象“default”/“kube-root-ca.crt
我只是尝试运行一个简单的批处理作业并收到此错误“卷“kube-api-access-cvwdt”的 MountVolume.SetUp 失败:对象“default”/“kube-root-ca.crt
我正在用KIND测试K8。。我创建了集群:。现在我想用sudo Kind删除集群来删除这个集群,但得到的是:。但是当我转到路径时,我看不到文件:。配置文件:。另外,当调用命令sudo种类删除集群--名
我在用kind测试k8。我创建了集群:。现在我想用sudo Kind删除集群来删除这个集群,但得到的是:。但当转到路径时,我没有看到文件:。配置文件:。另外,当调用命令sudo种类删除集群--名称节点
简介 kube-proxy 是 Kubernetes 集群中负责服务发现和负载均衡的组件之一。它是一个网络代理,运行在每个节点上, 用于 service 资源的负载均衡。它有两种模式:iptable
本文分享自华为云社区《kube-apiserver限流机制原理》,作者:可以交个朋友。 背景 apiserver是kubernetes中最重要的组件,一旦遇到恶意刷接口或请求量超过承载范围,api
kube-scheduler组件是kubernetes中的核心组件之一,主要负责pod资源对象的调度工作,具体来说,kube-scheduler组件负责根据调度算法(包括预选算法和优选算法)将未调度的
kube-scheduler组件是kubernetes中的核心组件之一,主要负责pod资源对象的调度工作,具体来说,kube-scheduler组件负责根据调度算法(包括预选算法和优选算法)将未调度的
kube-scheduler组件是kubernetes中的核心组件之一,主要负责pod资源对象的调度工作,具体来说,kube-scheduler组件负责根据调度算法(包括预选算法和优选算法)将未调度的
我通过docker-multinode设置了k8s $ https_proxy=http://10.25.30.127:7777 IP_ADDRESS=10.25.24.116 MASTER_IP=1
kube-proxy 有一个名为 --proxy-mode 的选项,根据帮助信息,该选项可以是 userspace 或 iptables。(见下文) # kube-proxy -h Usage of
在单节点Kubernetes集群上安装Kube-router时,遇到以下问题: kube-system kube-router-wnnq8 0/1
我是一名优秀的程序员,十分优秀!