kube-proxy的pod状态为containercreating处理方法和k8s创建pod状态为containercreating的处理方法

最新推荐文章于 2024-09-13 11:04:23 发布

D1561691

最新推荐文章于 2024-09-13 11:04:23 发布

阅读量1.1k

点赞数 10

分类专栏：程序员文章标签： kubernetes 容器云原生

本文链接：https://blog.csdn.net/D1561691/article/details/137362471

版权

当kube-proxy的pod状态显示为containercreating时，通常是由于缺少所需镜像导致。在内网环境中，需确保所有节点导入了必要的镜像，如calico/node、calico/kube-controllers等。通过`kubectl describe pod`命令可以定位具体异常，查看并解决镜像缺失问题。

摘要由CSDN通过智能技术生成

[root@worker-165 kubelet]# systemctl status kubelet

● kubelet.service - kubelet: The Kubernetes Node Agent

Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)

Drop-In: /usr/lib/systemd/system/kubelet.service.d

└─10-kubeadm.conf

Active: active (running) since 一 2021-11-29 16:56:51 CST; 1h 31min ago

Docs: https://kubernetes.io/docs/

Main PID: 9321 (kubelet)

Tasks: 16

Memory: 47.6M

CGroup: /system.slice/kubelet.service

└─9321 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --network-plugin=cni --pod-infra-container-image=regis…

11月 29 17:57:06 worker-165 kubelet[9321]: time=“2021-11-29T17:57:06+08:00” level=info msg=“About to acquire host-wide IPAM lock.” source=“ipam_plugin.go:348”

11月 29 17:57:06 worker-165 kubelet[9321]: time=“2021-11-29T17:57:06+08:00” level=info msg=“Acquired host-wide IPAM lock.” source=“ipam_plugin.go:363”

11月 29 17:57:06 worker-165 kubelet[9321]: 2021-11-29 17:57:06.931 [INFO][47594] ipam.go 1410: Releasing all IPs with handle ‘k8s-pod-network.6d4fb99e7785f3b4018584c3e3a799b097e3b5b54ebe93131fd5cf5a8a8e5cae’

11月 29 17:57:06 worker-165 kubelet[9321]: 2021-11-29 17:57:06.943 [WARNING][47594] ipam_plugin.go 424: Asked to release address but it doesn’t exist. Ignoring ContainerID="6d4fb99e7785f3b4018584c3e3a799b097e3b5b54ebe93131fd5cf5a8…

11月 29 17:57:06 worker-165 kubelet[9321]: 2021-11-29 17:57:06.943 [INFO][47594] ipam_plugin.go 435: Releasing address using workloadID ContainerID=“6d4fb99e7785f3b4018584c3e3a799b097e3b5b54ebe93131fd5cf5a8a8e5cae” HandleID="k8s-p…

11月 29 17:57:06 worker-165 kubelet[9321]: 2021-11-29 17:57:06.943 [INFO][47594] ipam.go 1410: Releasing all IPs with handle ‘kube-system.calico-kube-controllers-78d6f96c7b-tqxp4’

11月 29 17:57:06 worker-165 kubelet[9321]: time=“2021-11-29T17:57:06+08:00” level=info msg=“Released host-wide IPAM lock.” source=“ipam_plugin.go:369”

11月 29 17:57:06 worker-165 kubelet[9321]: 2021-11-29 17:57:06.949 [INFO][47586] k8s.go 576: Teardown processing complete. ContainerID=“6d4fb99e7785f3b4018584c3e3a799b097e3b5b54ebe93131fd5cf5a8a8e5cae”

11月 29 17:57:07 worker-165 kubelet[9321]: I1129 17:57:07.119675 9321 pod_container_deletor.go:79] “Container not found in pod’s containers” containerID=“d6d7faa88f9cc1a5645540c9035a1cb0a472583c1d6ac23c9293bee77eb0f573”

11月 29 17:57:07 worker-165 kubelet[9321]: I1129 17:57:07.119765 9321 pod_container_deletor.go:79] “Container not found in pod’s containers” containerID=“ecab3db290102ab0d7a54510f30f957c0edc759cce0f176f2f40231ca3024b5d”

Hint: Some lines were ellipsized, use -l to show in full.

[root@worker-165 kubelet]#

kube-proxy的pod状态为containercreating说明及处理

============================================&#