calico-node一直restart
来源:5-8 DNS插件-CoreDNS
nnglong
2021-05-25
node-2 ip地址信息
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:08:06:61 brd ff:ff:ff:ff:ff:ff
inet 10.155.19.64/24 brd 10.155.19.255 scope global noprefixroute ens33:1
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fe08:661/64 scope link
valid_lft forever preferred_lft forever
node-3 ip地址信息
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:b9:2d:30 brd ff:ff:ff:ff:ff:ff
inet 10.155.19.147/24 brd 10.155.19.255 scope global noprefixroute ens33:1
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:feb9:2d30/64 scope link
valid_lft forever preferred_lft forever
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 46:d3:b2:62:cb:74 brd ff:ff:ff:ff:ff:ff
4: kube-ipvs0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether e6:34:63:c5:6c:e2 brd ff:ff:ff:ff:ff:ff
inet 10.233.0.1/32 scope global kube-ipvs0
valid_lft forever preferred_lft forever
5: tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
inet 10.200.139.64/32 scope global tunl0
valid_lft forever preferred_lft forever
node-2 部署了master和worker。
node-3 部署了worker。
缺少ip会导致node-2 calico 起不来吗。
以下是node-2 pod Events
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 6m46s default-scheduler Successfully assigned kube-system/calico-node-mbqzb to node-2
Normal Pulled 6m45s kubelet Container image "docker.io/calico/cni:v3.19.1" already present on machine
Normal Created 6m45s kubelet Created container upgrade-ipam
Normal Started 6m45s kubelet Started container upgrade-ipam
Normal Pulled 6m44s kubelet Container image "docker.io/calico/cni:v3.19.1" already present on machine
Normal Created 6m44s kubelet Created container install-cni
Normal Started 6m44s kubelet Started container install-cni
Normal Pulled 6m42s kubelet Container image "docker.io/calico/pod2daemon-flexvol:v3.19.1" already present on machine
Normal Created 6m42s kubelet Created container flexvol-driver
Normal Started 6m41s kubelet Started container flexvol-driver
Normal Pulled 6m41s kubelet Container image "docker.io/calico/node:v3.19.1" already present on machine
Normal Created 6m41s kubelet Created container calico-node
Normal Started 6m40s kubelet Started container calico-node
Warning Unhealthy 5m42s (x6 over 6m32s) kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/bird/bird.ctl: connect: no such file or directory
Warning Unhealthy 5m33s (x3 over 6m3s) kubelet Liveness probe failed: calico/node is not ready: Felix is not live: Get "http://localhost:9099/liveness": dial tcp [::1]:9099: connect: connection refused
Normal Killing 5m33s kubelet Container calico-node failed liveness probe, will be restarted
Warning Unhealthy 103s (x12 over 6m23s) kubelet Liveness probe failed: calico/node is not ready: bird/confd is not live: exit status 1
写回答
1回答
-
刘果国
2021-05-26
看看node-2的系统日志和calico容器的启动日志。另外可以从node-2和node-3区别入手
00
相似问题