是这样的,我想要配置ingress-nginx:v1.8.1,成功应用了yaml文件,但是查看pod的时候,发现状态为CrashLoopBackOff,这个要怎么解决?
[root@master-140 /data/yaml]# kubectl apply -f ingress.yaml
namespace/ingress-nginx created
serviceaccount/ingress-nginx created
serviceaccount/ingress-nginx-admission created
role.rbac.authorization.k8s.io/ingress-nginx created
role.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrole.rbac.authorization.k8s.io/ingress-nginx created
clusterrole.rbac.authorization.k8s.io/ingress-nginx-admission created
rolebinding.rbac.authorization.k8s.io/ingress-nginx created
rolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
configmap/ingress-nginx-controller created
service/ingress-nginx-controller created
service/ingress-nginx-controller-admission created
deployment.apps/ingress-nginx-controller created
job.batch/ingress-nginx-admission-create created
job.batch/ingress-nginx-admission-patch created
ingressclass.networking.k8s.io/nginx created
validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission created
[root@master-140 /data/yaml]#
[root@master-140 /data/yaml]#
[root@master-140 /data/yaml]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
ingress-nginx ingress-nginx-admission-create-94zfc 0/1 Completed 0 3s
ingress-nginx ingress-nginx-admission-patch-bf8zq 0/1 Completed 1 (2s ago) 3s
ingress-nginx ingress-nginx-controller-76d4c946c8-xhdrx 0/1 ContainerCreating 0 3s
kube-system calico-kube-controllers-85578c44bf-hn4j8 1/1 Running 5 (134m ago) 5d23h
kube-system calico-node-9n7sz 1/1 Running 5 (134m ago) 5d23h
kube-system calico-node-t67r6 1/1 Running 4 (9h ago) 5d23h
kube-system calico-node-tptgn 1/1 Running 5 (9h ago) 5d23h
kube-system calico-node-wkvxk 1/1 Running 4 (9h ago) 5d23h
kube-system calico-node-xwttn 1/1 Running 4 (9h ago) 5d23h
kube-system coredns-65dcc469f7-5ffpp 1/1 Running 5 (9h ago) 14d
kube-system coredns-65dcc469f7-7n5ld 1/1 Running 5 (9h ago) 14d
kube-system etcd-master-140 1/1 Running 3 (134m ago) 3d23h
kube-system etcd-master-141 1/1 Running 2 (9h ago) 3d23h
kube-system etcd-master-142 1/1 Running 7 (9h ago) 12d
kube-system kube-apiserver-master-140 1/1 Running 1 (134m ago) 168m
kube-system kube-apiserver-master-141 1/1 Running 0 167m
kube-system kube-apiserver-master-142 1/1 Running 0 166m
kube-system kube-controller-manager-master-140 1/1 Running 8 (134m ago) 14d
kube-system kube-controller-manager-master-141 1/1 Running 5 (9h ago) 13d
kube-system kube-controller-manager-master-142 1/1 Running 10 (166m ago) 12d
kube-system kube-proxy-49pt2 1/1 Running 6 (134m ago) 14d
kube-system kube-proxy-5qtd4 1/1 Running 5 (9h ago) 12d
kube-system kube-proxy-7vhlv 1/1 Running 5 (9h ago) 12d
kube-system kube-proxy-h87z8 1/1 Running 5 (9h ago) 13d
kube-system kube-proxy-rrhvx 1/1 Running 7 (9h ago) 12d
kube-system kube-scheduler-master-140 1/1 Running 8 (134m ago) 14d
kube-system kube-scheduler-master-141 1/1 Running 6 (9h ago) 13d
kube-system kube-scheduler-master-142 1/1 Running 9 (166m ago) 12d
应用清单文件的时候没有出现任何报错,查看pod状态时才发现, ingress-nginx-controller-76d4c946c8-xhdrx 这个pod状态是ContainerCreating,本人describe查看详细信息发现容器退出码为127。failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/nginx-ingress-controller": stat /nginx-ingress-controller: no such file or directory: unknown
这个官方下载的ingress-nginx的yaml文件我就只改了镜像,其他没修改,有没有大佬能够指点一下
[root@master-140 /data/yaml]# kubectl describe pod ingress-nginx-controller-76d4c946c8-xhdrx -n ingress-nginx
Name: ingress-nginx-controller-76d4c946c8-xhdrx
Namespace: ingress-nginx
Priority: 0
Service Account: ingress-nginx
Node: node-144/192.168.10.144
Start Time: Sun, 06 Aug 2023 21:31:47 +0800
Labels: app.kubernetes.io/component=controller
app.kubernetes.io/instance=ingress-nginx
app.kubernetes.io/name=ingress-nginx
app.kubernetes.io/part-of=ingress-nginx
app.kubernetes.io/version=1.8.1
pod-template-hash=76d4c946c8
Annotations: cni.projectcalico.org/containerID: 7ba5d7cfd75252caf9b8f8e34d2c1b0f2d6cecebcff73769baf6016144b03464
cni.projectcalico.org/podIP: 10.244.227.203/32
cni.projectcalico.org/podIPs: 10.244.227.203/32
Status: Running
IP: 10.244.227.203
IPs:
IP: 10.244.227.203
Controlled By: ReplicaSet/ingress-nginx-controller-76d4c946c8
Containers:
controller:
Container ID: docker://073a8a2ec2e917ede973863154eb2bf830a5e5b44e55db7e2035759874b2eb8f
Image: wyx.harbor.com/myrepo/ingress:v1.8.1
Image ID: docker-pullable://wyx.harbor.com/myrepo/ingress@sha256:0c183828ec41fe04f54bd357884bd4d656529db696b20e7bb9e7ffc837ed264a
Ports: 80/TCP, 80/TCP, 2443/TCP, 8443/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP
Args:
/nginx-ingress-controller
--publish-service=$(POD_NAMESPACE)/ingress-nginx-controller
--election-id=ingress-nginx-leader
--controller-class=k8s.io/ingress-nginx
--ingress-class=nginx
--configmap=$(POD_NAMESPACE)/ingress-nginx-controller
--validating-webhook=:8443
--validating-webhook-certificate=/usr/local/certificates/cert
--validating-webhook-key=/usr/local/certificates/key
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: ContainerCannotRun
Message: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/nginx-ingress-controller": stat /nginx-ingress-controller: no such file or directory: unknown
Exit Code: 127
Started: Sun, 06 Aug 2023 21:47:51 +0800
Finished: Sun, 06 Aug 2023 21:47:51 +0800
Ready: False
Restart Count: 8
Requests:
cpu: 100m
memory: 90Mi
Liveness: http-get http://:10254/healthz delay=10s timeout=1s period=10s #success=1 #failure=5
Readiness: http-get http://:10254/healthz delay=10s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAME: ingress-nginx-controller-76d4c946c8-xhdrx (v1:metadata.name)
POD_NAMESPACE: ingress-nginx (v1:metadata.namespace)
LD_PRELOAD: /usr/local/lib/libmimalloc.so
Mounts:
/usr/local/certificates/ from webhook-cert (ro)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rntvs (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
webhook-cert:
Type: Secret (a volume populated by a Secret)
SecretName: ingress-nginx-admission
Optional: false
kube-api-access-rntvs:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: kubernetes.io/os=linux
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 20m default-scheduler Successfully assigned ingress-nginx/ingress-nginx-controller-76d4c946c8-xhdrx to node-144
Warning FailedMount 20m (x2 over 20m) kubelet MountVolume.SetUp failed for volume "webhook-cert" : secret "ingress-nginx-admission" not found
Normal Created 19m (x4 over 20m) kubelet Created container controller
Warning Failed 19m (x4 over 20m) kubelet Error: failed to start container "controller": Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/nginx-ingress-controller": stat /nginx-ingress-controller: no such file or directory: unknown
Normal Pulled 18m (x5 over 20m) kubelet Container image "wyx.harbor.com/myrepo/ingress:v1.8.1" already present on machine
Warning BackOff 22s (x103 over 20m) kubelet Back-off restarting failed container controller in pod ingress-nginx-controller-76d4c946c8-xhdrx_ingress-nginx(7f87ee6e-36eb-4641-be53-589aea769db7)
[root@master-140 /data/yaml]# kubectl logs ingress-nginx-controller-76d4c946c8-xhdrx -n ingress-nginx
[root@master-140 /data/yaml]#