Openstack 库伯内特斯。无法从主机连接到任何pod
我正在尝试在Openstack+CoreOS中设置Kubernetes 我有10.240.63.84主人和2个63和83仆从。我还创建了3个redis吊舱:Openstack 库伯内特斯。无法从主机连接到任何pod,openstack,coreos,kubernetes,Openstack,Coreos,Kubernetes,我正在尝试在Openstack+CoreOS中设置Kubernetes 我有10.240.63.84主人和2个63和83仆从。我还创建了3个redis吊舱: redis-gopher-gziey 10.244.32.2 10.240.63.66/10.240.63.66 redis-managed-oh43e 10.244.32.3 10.240.63.66/10.240.63.66 redis-primary-fplln 10.244.54.
redis-gopher-gziey 10.244.32.2 10.240.63.66/10.240.63.66
redis-managed-oh43e 10.244.32.3 10.240.63.66/10.240.63.66
redis-primary-fplln 10.244.54.2 10.240.63.83/10.240.63.83
主机的路由表如下所示:
10.240.63.0 * 255.255.255.0 U 0 0 0 eth0
10.240.63.1 * 255.255.255.255 UH 1024 0 0 eth0
10.244.0.0 * 255.255.0.0 U 0 0 0 flannel.1
10.244.50.0 * 255.255.255.0 U 0 0 0 docker0
ifconfig-a的输出是:
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.244.50.1 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fe80::542f:6fff:fe4a:adf3 prefixlen 64 scopeid 0x20<link>
ether 56:84:7a:fe:97:99 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1 bytes 90 (90.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.240.63.84 netmask 255.255.255.0 broadcast 10.240.63.255
inet6 fe80::f816:3eff:fe89:e9a0 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:89:e9:a0 txqueuelen 1000 (Ethernet)
RX packets 430706 bytes 559764129 (533.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 238519 bytes 116083693 (110.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet 10.244.50.0 netmask 255.255.0.0 broadcast 0.0.0.0
inet6 fe80::601f:62ff:feed:1556 prefixlen 64 scopeid 0x20<link>
ether 62:1f:62:ed:15:56 txqueuelen 0 (Ethernet)
RX packets 20 bytes 1504 (1.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 79 bytes 7686 (7.5 KiB)
TX errors 0 dropped 19 overruns 0 carrier 0 collisions 0
仆从:
- name: flanneld.service
command: start
drop-ins:
- name: 50-network-config.conf
content: |
[Service]
ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{"Network":"10.244.0.0/16", "Backend": {"Type": "vxlan"}}'
ExecStart=
ExecStart=/usr/libexec/sdnotify-proxy /run/flannel/sd.sock \
/usr/bin/docker run --net=host --privileged=true --rm \
--volume=/run/flannel:/run/flannel \
--env=NOTIFY_SOCKET=/run/flannel/sd.sock \
--env-file=/run/flannel/options.env \
--volume=${ETCD_SSL_DIR}:/etc/ssl/etcd:ro \
quay.io/coreos/flannel:${FLANNEL_VER} /opt/bin/flanneld -etcd-endpoints http://10.240.63.84:4001 --ip-masq=true --iface=eth0
因此,问题是我无法从master ping任何pod,也无法连接到任何端口,错误是:
ncat -v -t 10.244.32.2 6379
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: No route to host.
这种事情很难远程调试。我要检查的事项: 1) 在发送方:
iptables-t原始-I输出-d 10.244.32.2-j跟踪;dmesg-c>/dev/null;ncat-v-t 10.244.32.2 6379;dmesg代码>
这将使您对内核正在做什么有一些了解
2) 在发送方上:tcpdump-i任意主机10.244.32.2
&ncat-v-t 10.244.32.2 6379`
这将提供更多的洞察力
3) 在接收器上:iptables-t原始-I输出-d 10.244.32.2-j跟踪;dmesg-c>/dev/null;ncat-v-t 10.244.32.2 6379;dmesg代码>
这将告诉您数据包是否通过封装
您需要基本上通过整个连接来验证管道。您是否尝试过在虚拟机上禁用iptables或打开iptables中的端口和ICMP?
ncat -v -t 10.244.32.2 6379
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: No route to host.