kubernetes成功安装dashboard后，第二天无法访问

Question

[root@m3 ~]# kubectl describe pods -n kube-system kubernetes-dashboard-5bd4bfc87-wqpbc
Name:               kubernetes-dashboard-5bd4bfc87-wqpbc
Namespace:          kube-system
Priority:           2000000000
PriorityClassName:  system-cluster-critical
Node:               s2/192.168.32.147
Start Time:         Fri, 12 Jul 2019 20:39:51 +0800
Labels:             k8s-app=kubernetes-dashboard
                    pod-template-hash=5bd4bfc87
Annotations:        cni.projectcalico.org/podIP: 172.22.3.26/32
                    scheduler.alpha.kubernetes.io/critical-pod: 
                    seccomp.security.alpha.kubernetes.io/pod: docker/default
Status:             Running
IP:                 172.22.3.26
Controlled By:      ReplicaSet/kubernetes-dashboard-5bd4bfc87
Containers:
  kubernetes-dashboard:
    Container ID:  docker://c21fb17eb38f9f0c8eabe49b4940659f171c893f31580d97f10c654268134c05
    Image:         registry.cn-hangzhou.aliyuncs.com/imooc/kubernetes-dashboard-amd64:v1.8.3
    Image ID:      docker-pullable://registry.cn-hangzhou.aliyuncs.com/imooc/kubernetes-dashboard-amd64@sha256:050620264fb56824b1bc1b9876f9c17875d96bb9fb96d5c34027ddbf65786f62
    Port:          8443/TCP
    Host Port:     0/TCP
    Args:
      --auto-generate-certificates
    State:          Running
      Started:      Sun, 14 Jul 2019 16:09:41 +0800
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Sun, 14 Jul 2019 14:39:30 +0800
      Finished:     Sun, 14 Jul 2019 16:03:21 +0800
    Ready:          True
    Restart Count:  9
    Limits:
      cpu:     100m
      memory:  300Mi
    Requests:
      cpu:        50m
      memory:     100Mi
    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 kubernetes-dashboard-token-6cl4d (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  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>
  kubernetes-dashboard-token-6cl4d:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-token-6cl4d
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     CriticalAddonsOnly
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason          Age                  From         Message
  ----     ------          ----                 ----         -------
  Warning  Unhealthy       53m (x2 over 53m)    kubelet, s2  Liveness probe failed: Get https://172.22.3.23:8443/: dial tcp 172.22.3.23:8443: connect: invalid argument
  Normal   SandboxChanged  48m (x25 over 138m)  kubelet, s2  Pod sandbox changed, it will be killed and re-created.

Answer 1

刘果国 2019-07-14 07:33:31

访问有什么异常呢？

• 提问者 慕标0284258 #1

  无法在物理机用https进行访问，物理机telnet这个30005端口是不通的

• 刘果国 回复 提问者 慕标0284258 #2

  看端口状态都是监听了，如果telnet还不通的话不应该了，先ping看网络是否通，看看机器又什么网络限制，最后还不行就得用工具抓包了

• 提问者 慕标0284258 回复 刘果国 #3

  我再试下

点开查看后面1条评论