kubernetes-dashboard Pod CrashLoopBackOff

来源:4-10 安装Dashboard

慕圣7354801

2021-10-09

kubernetes-dashboard 这个 pod 一直 CrashLoopBackOff

[root@master kubeblog]# kubectl get pods -n kubernetes-dashboard
NAME                                         READY   STATUS             RESTARTS      AGE
dashboard-metrics-scraper-856586f554-jhkqz   1/1     Running            0             20m
kubernetes-dashboard-7b9b87bb74-4qlk4        0/1     CrashLoopBackOff   8 (12s ago)   20m

kubectl descripe pod 显示它无法连接自己的 443 端口?10.9.1.14是它自己的 IP 地址啊,为什么无法连接?

[root@master kubeblog]# kubectl describe pod kubernetes-dashboard-7b9b87bb74-4qlk4 -n kubernetes-dashboard
Name:         kubernetes-dashboard-7b9b87bb74-4qlk4
Namespace:    kubernetes-dashboard
Priority:     0
Node:         node1/192.168.200.11
Start Time:   Sat, 09 Oct 2021 23:34:10 +0800
Labels:       k8s-app=kubernetes-dashboard
              pod-template-hash=7b9b87bb74
Annotations:  <none>
Status:       Running
IP:           10.9.1.14
IPs:
  IP:           10.9.1.14
Controlled By:  ReplicaSet/kubernetes-dashboard-7b9b87bb74
Containers:
  kubernetes-dashboard:
    Container ID:  docker://53ff66e44a23ec227ed427e151f6d969df3e5a577d33b90b6b005724e873c040
    Image:         kubernetesui/dashboard:v2.3.1
    Image ID:      docker-pullable://docker.io/kubernetesui/dashboard@sha256:ec27f462cf1946220f5a9ace416a84a57c18f98c777876a8054405d1428cc92e
    Port:          8443/TCP
    Host Port:     0/TCP
    Args:
      --auto-generate-certificates
      --namespace=kubernetes-dashboard
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Sat, 09 Oct 2021 23:54:17 +0800
      Finished:     Sat, 09 Oct 2021 23:54:47 +0800
    Ready:          False
    Restart Count:  8
    Liveness:       http-get https://:8443/ delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /certs from kubernetes-dashboard-certs (rw)
      /tmp from tmp-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dxlzt (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kubernetes-dashboard-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-certs
    Optional:    false
  tmp-volume:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-dxlzt:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 node-role.kubernetes.io/master:NoSchedule
                             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 kubernetes-dashboard/kubernetes-dashboard-7b9b87bb74-4qlk4 to node1
  Warning  Unhealthy  20m                   kubelet            Liveness probe failed: Get "https://10.9.1.14:8443/": dial tcp 10.9.1.14:8443: connect: connection refused
  Normal   Started    18m (x4 over 20m)     kubelet            Started container kubernetes-dashboard
  Normal   Created    16m (x5 over 20m)     kubelet            Created container kubernetes-dashboard
  Warning  BackOff    5m26s (x56 over 19m)  kubelet            Back-off restarting failed container
  Normal   Pulled     34s (x9 over 20m)     kubelet            Container image "kubernetesui/dashboard:v2.3.1" already present on machine
写回答

1回答

清风

2021-10-12

问题解决了吗,是不是服务没起来

0
0

Kubernetes 入门到进阶实战,系统性掌握 K8s 生产实践

阿里云最有价值专家亲授,云原生时代必备技能

1517 学习 · 616 问题

查看课程