pod 无法启动。状态为Completed

来源:6-6 部署ingress-nginx(下)

宝慕林9524590

2020-05-08

ingress-nginx pod状态是 Completed

NAME                                        READY   STATUS      RESTARTS   AGE
ingress-nginx-admission-create-5bjw4        0/1     Completed   0          28m
ingress-nginx-admission-patch-5mx5w         0/1     Completed   1          28m

通过查询描述

 kubectl describe pod  -n ingress-nginx ingress-nginx-admission-create-5bjw4
Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               31m   default-scheduler  Successfully assigned ingress-nginx/ingress-nginx-admission-create-5bjw4 to node-173
  Normal   Pulled                  31m   kubelet, node-173  Container image "jettech/kube-webhook-certgen:v1.2.0" already present on machine
  Normal   Created                 31m   kubelet, node-173  Created container create
  Normal   Started                 31m   kubelet, node-173  Started container create
  Normal   SandboxChanged          31m   kubelet, node-173  Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  31m   kubelet, node-173  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "ingress-nginx-admission-create-5bjw4": Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused "process_linux.go:413: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: time=\\\"2020-05-08T10:56:28+08:00\\\" level=fatal msg=\\\"no such file or directory\\\"\\n\""": unknown

请问一下,这个是什么问题?

写回答

1回答

刘果国

2020-05-09

你好,这个是新版本的吧,没玩过啊,不过这两个completed的pod就是job类型的,运行完成了,没问题的。从名字看应该是准入控制相关的pod,做一些初始化类的工作。

0
0

Kubernetes生产落地全程实践

一个互联网公司落地Kubernetes全过程点点滴滴

2293 学习 · 2216 问题

查看课程