Pod无法在PodCIDR中获取IP,获取docker ip

时间:2017-04-26 05:11:27

标签: docker kubernetes calico

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"}

环境: - 云提供商或硬件配置: - 操作系统(例如来自/ etc / os-release):CentOS 7.2 - 内核(例如uname -a):4.9.0 - 安装工具:裸机

发生了什么: 将新节点添加到现有群集,并将pod安排到新节点。 pod的IP不在PodCIDR的范围内,并使用docker bridge 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

和pod

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-8bnr1nginx-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

任何可以帮助我的人?我试着解决两天的费用。 THX非常多!

1 个答案:

答案 0 :(得分:0)

此问题已解决,我关闭了此问题。 问题是我在kubelet.service中的cni配置标志处注释了我稍后添加到集群的节点