就绪探测失败:超时:在1s内连接服务":8080“失败

Question

我正在尝试使用minikube构建微服务镜像并将其部署到我的开发机器上运行的单节点Kubernetes集群。我正在使用Google的云原生微服务在线精品店演示应用程序，以了解Kubernetes、Istio等技术的使用。

github存储库链接：microservices-demo

我遵循了所有的安装过程，在本地构建和部署微服务，并且能够通过我的浏览器访问web前端。但是，当我单击任何产品图片时，我会看到这个错误页面。

HTTP Status: 500 Internal Server Error

在使用kubectl get pod进行检查时，我意识到我的一个pod(推荐服务)的状态为CrashLoopBackOff。运行kubectl describe pods recommendationservice-55b4d6c477-kxv8r

Namespace:    default
Priority:     0
Node:         minikube/192.168.99.116
Start Time:   Thu, 23 Jul 2020 19:58:38 +0530
Labels:       app=recommendationservice
              app.kubernetes.io/managed-by=skaffold-v1.11.0
              pod-template-hash=55b4d6c477
              skaffold.dev/builder=local
              skaffold.dev/cleanup=true
              skaffold.dev/deployer=kubectl
              skaffold.dev/docker-api-version=1.40
              skaffold.dev/run-id=49913ced-e8df-40a7-9336-a227b56bcb5f
              skaffold.dev/tag-policy=git-commit
Annotations:  <none>
Status:       Running
IP:           172.17.0.14
IPs:
  IP:           172.17.0.14
Controlled By:  ReplicaSet/recommendationservice-55b4d6c477
Containers:
  server:
    Container ID:   docker://2d92aa966a82fbe58c8f40f6ecf9d6d55c29f8081cb40e0423a2397e1419350f
    Image:          recommendationservice:2216d526d249cc8363129aed9a09d752f9ad8f458e61e50a2a99c59d000606cb
    Image ID:       docker://sha256:2216d526d249cc8363129aed9a09d752f9ad8f458e61e50a2a99c59d000606cb
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Thu, 23 Jul 2020 21:09:33 +0530
      Finished:     Thu, 23 Jul 2020 21:09:53 +0530
    Ready:          False
    Restart Count:  29
    Limits:
      cpu:     200m
      memory:  450Mi
    Requests:
      cpu:      100m
      memory:   220Mi
    Liveness:   exec [/bin/grpc_health_probe -addr=:8080] delay=0s timeout=1s period=5s #success=1 #failure=3
    Readiness:  exec [/bin/grpc_health_probe -addr=:8080] delay=0s timeout=1s period=5s #success=1 #failure=3
    Environment:
      PORT:                          8080
      PRODUCT_CATALOG_SERVICE_ADDR:  productcatalogservice:3550
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-sbpcx (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-sbpcx:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-sbpcx
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Pulled     44m (x15 over 74m)     kubelet, minikube  Container image "recommendationservice:2216d526d249cc8363129aed9a09d752f9ad8f458e61e50a2a99c59d000606cb" already present on machine
  Warning  Unhealthy  9m33s (x99 over 74m)   kubelet, minikube  Readiness probe failed: timeout: failed to connect service ":8080" within 1s
  Warning  BackOff    4m25s (x294 over 72m)  kubelet, minikube  Back-off restarting failed container

在活动中，我看到了Readiness probe failed: timeout: failed to connect service ":8080" within 1s。原因是什么?我如何解决这个问题？谢谢你的帮助！

Answer 1

回答

就绪探测超时(%1秒)太短。

更多信息

定义相关的就绪探测器，以便在server容器内运行/bin/grpc_health_probe -addr=:8080。

您可能期望1秒的超时对于这样的探测足够了，但是这是在Minikube上运行的，所以这可能会影响探测的超时。