创建pod一直处于Pending

网友投稿 254 2022-10-29

创建pod一直处于Pending

故障现象:

[root@master01 12:37:23]:/root/k8s #kubectl get pods,svc NAME READY STATUS RESTARTS AGE pod/mypod 1/1 Running 2 12h pod/nginx-7697996758-5rtnw 1/1 Running 3 37h pod/nginx-7697996758-rvzsh 1/1 Running 3 25h pod/nginx-7697996758-zxfbp 1/1 Running 3 37h pod/tomcat-749f7974b6-cw98w 0/1 Pending 0 89s pod/tomcat-749f7974b6-plr6b 0/1 Pending 0 89s pod/tomcat-749f7974b6-qrs9l 0/1 Pending 0 89s [root@master01 12:37:25]:/root/k8s #kubectl describe pod tomcat-749f7974b6-qrs9l Name: tomcat-749f7974b6-qrs9l Namespace: default Priority: 0 PriorityClassName: Node: Labels: app=tomcat pod-template-hash=749f7974b6 Annotations: Status: Pending IP: Controlled By: ReplicaSet/tomcat-749f7974b6 Containers: tomcat: Image: tomcat:latest Port: 8080/TCP Host Port: 0/TCP Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-sxx8q (ro) Conditions: Type Status PodScheduled False Volumes: default-token-sxx8q: Type: Secret (a volume populated by a Secret) SecretName: default-token-sxx8q Optional: false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- #故障报错 Warning FailedScheduling 118s (x2 over 118s) default-scheduler 0/2 nodes are available: 2 node(s) had taints that the pod didn't tolerate. #发现该节点是不可调度的 [root@master01 12:37:54]:/root/k8s #kubectl get no -o yaml | grep taint -A 5 taints: - effect: NoSchedule key: node.kubernetes.io/unreachable timeAdded: 2020-04-23T03:38:16Z status: addresses: -- taints: - effect: NoSchedule key: node.kubernetes.io/unreachable timeAdded: 2020-04-23T03:38:16Z status: addresses:

故障原因:pod连接master网络异常,恢复即可因为kubernetes出于安全考虑默认情况下无法在master节点上部署pod

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:Service Mesh 最火项目 Istio 分层架构,你真的了解吗?
下一篇:基于嵌入式技术的智能仪器触摸屏接口设计
相关文章

 发表评论

暂时没有评论,来抢沙发吧~