Pod无法在PodCIDR获取IP，获取docker ip

Question

Kubernetes 版本（使用kubectl version）：

Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:33:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

环境： - 云提供商或硬件配置： - OS（例如来自 /etc/os-release）：美分OS 7.2 - 内核（例如uname -a）：4.9.0 - 安装工具：裸机

发生了什么事：将新节点添加到现有集群，并将 pod 调度到新节点。 pod的IP不在PodCIDR范围内，使用docker网桥IP

dl.240.172.hadoop.sjz   Ready,master   18d       v1.6.1
dl.245.0.hadoop.sjz     Ready          36m       v1.6.1
dl.245.1.hadoop.sjz     Ready          36m       v1.6.1
dl.245.11.hadoop.sjz    Ready          28m       v1.6.1
dl.245.12.hadoop.sjz    Ready          28m       v1.6.1
dl.245.13.hadoop.sjz    Ready          28m       v1.6.1
dl.245.14.hadoop.sjz    Ready          28m       v1.6.1
dl.245.15.hadoop.sjz    Ready          28m       v1.6.1
dl.245.16.hadoop.sjz    Ready          28m       v1.6.1
dl.245.17.hadoop.sjz    Ready          28m       v1.6.1
dl.245.18.hadoop.sjz    Ready          28m       v1.6.1
dl.245.19.hadoop.sjz    Ready          28m       v1.6.1
dl.245.2.hadoop.sjz     Ready          36m       v1.6.1
dl.245.3.hadoop.sjz     Ready          36m       v1.6.1
dl.245.5.hadoop.sjz     Ready          18d       v1.6.1
dl.245.6.hadoop.sjz     Ready          18d       v1.6.1
dl.245.7.hadoop.sjz     Ready          18d       v1.6.1
dl.245.8.hadoop.sjz     Ready          18d       v1.6.1
dl.245.9.hadoop.sjz     Ready          18d       v1.6.1
l22-240-170             Ready          2h        v1.6.1
l22-240-171             Ready,master   18d       v1.6.1

跟随的节点是新的：

dl.245.0.hadoop.sjz     Ready          36m       v1.6.1
dl.245.1.hadoop.sjz     Ready          36m       v1.6.1
dl.245.11.hadoop.sjz    Ready          28m       v1.6.1
dl.245.12.hadoop.sjz    Ready          28m       v1.6.1
dl.245.13.hadoop.sjz    Ready          28m       v1.6.1
dl.245.14.hadoop.sjz    Ready          28m       v1.6.1
dl.245.15.hadoop.sjz    Ready          28m       v1.6.1
dl.245.16.hadoop.sjz    Ready          28m       v1.6.1
dl.245.17.hadoop.sjz    Ready          28m       v1.6.1
dl.245.18.hadoop.sjz    Ready          28m       v1.6.1
dl.245.19.hadoop.sjz    Ready          28m       v1.6.1
dl.245.2.hadoop.sjz     Ready          36m       v1.6.1
dl.245.3.hadoop.sjz     Ready          36m       v1.6.1

和广告连播

auto-discovery-4253124847-h1ln1   1/1       Running   0          2h        10.244.124.200   l22-240-171
busybox                           1/1       Running   3          15d       10.244.71.2      dl.245.6.hadoop.sjz
gpu-test                          1/1       Running   4          15d       10.244.71.7      dl.245.6.hadoop.sjz
gpu-test1                         1/1       Running   3          13d       10.244.71.8      dl.245.6.hadoop.sjz
gpu-test1-1-2                     1/1       Running   3          10d       10.244.203.12    dl.245.8.hadoop.sjz
gpu-test1-1-3                     1/1       Running   2          9d        10.244.71.16     dl.245.6.hadoop.sjz
gpu-test12                        1/1       Running   3          11d       10.244.239.73    dl.245.9.hadoop.sjz
nginx-2970154533-wwb3l            1/1       Running   0          17m       172.17.0.2       dl.245.19.hadoop.sjz
test-ssh-1-lxfgq                  1/1       Running   0          9d        10.244.33.18     dl.245.5.hadoop.sjz
wanglinhong-mount-7jtv1           1/1       Running   0          2d        10.244.71.24     dl.245.6.hadoop.sjz
wanglinhong-test-wrvxv            1/1       Running   0          4d        10.244.239.94    dl.245.9.hadoop.sjz
wanglinhong-test3-8bnr1           1/1       Running   0          33m       172.17.0.2       dl.245.2.hadoop.sjz
wanglinhong-web-z37nb             1/1       Running   0          1d        10.244.203.31    dl.245.8.hadoop.sjz

pod wanglinhong-test3-8bnr1 和 nginx-2970154533-wwb3l 具有到新节点的 bean 调度。并且 ip 是 172.17.0.x

新节点的kubelet都有如下日志

Apr 26 11:35:04 dl.245.11.hadoop.sjz kubelet[25363]: I0426 11:35:04.182974   25363 kuberuntime_manager.go:902] updating runtime config through cri with podcidr 10.244.48.0/24

Apr 26 11:35:04 dl.245.11.hadoop.sjz kubelet[25363]: I0426 11:35:04.183206   25363 docker_service.go:277] docker cri received runtime config &RuntimeConfig{NetworkConfig:&NetworkConfig{PodCidr:10.244.48.0/24,},}

Apr 26 11:35:04 dl.245.11.hadoop.sjz kubelet[25363]: I0426 11:35:04.183445   25363 kubelet_network.go:326] Setting Pod CIDR:  -> 10.244.x.0/24

谁能帮帮我？我试着解决成本两天。非常感谢！

Answer 1

这个问题已经解决，关闭这个issue。问题是我在稍后添加到集群的节点 kubelet.service 中评论了 cni 配置标志

Pod无法在PodCIDR获取IP，获取docker ip

Pod cannot get IP in PodCIDR, get the docker ip

calico

docker

kubernetes