简体   繁体   English

Pod保持在ContainerCreating状态,并显示“ Failed create pod sand sandbox”消息

[英]Pods stay in ContainerCreating state with “Failed create pod sandbox” message

Performed an upgrade of K8S AWS cluster from 1.8.4 to 1.9.8 using kops. 使用kops将K8S AWS集群从1.8.4升级到1.9.8。

All "development" pods and some pods from kube-system namespace (cluster-autoscaler, kube-dns, kube-dns-autoscaler, kubernetes-dashboard, heapster) stuck in " ContainerCreating " state. 所有“开发”容器和来自kube系统名称空间的一些容器(集群自动缩放器,kube-dns,kube-dns-自动缩放器,kubernetes-仪表板,hashster)都处于“ ContainerCreating ”状态。

Pods describe command shows message: " Failed create pod sandbox " and " Pod sandbox changed, it will be killed and re-created. " Pod describe命令显示消息:“ 创建 Pod沙箱 失败 ”和“ Pod沙箱已更改,它将被杀死并重新创建。

Any ideas what could be the reason for such behavior or how to fix it? 任何想法可能是这种行为的原因或如何解决?

This is becoming a FAQ 这正在成为常见问题

But Pod sandbox errors are almost always CNI failures , which goes double for your situation since I don't know that 1.8 even used CNI 但是Pod沙箱错误几乎总是CNI故障 ,这对您来说是两倍,因为我不知道1.8甚至使用过CNI

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM