2

我正在尝试在我的掌舵图部署模板中实现一个简单的活跃度探测。下面是我的活性探针配置。Spring boot/actuator/health端点用作健康检查端点。

containers:
        - name: {{ .Release.Name }}-container
          image: {{ .Values.container.image }}
          ports:
            - containerPort: 8080
          livenessProbe:
            httpGet:
              path: /actuator/health
              port: 8080
            failureThreshold: 5
            periodSeconds: 10
            initialDelaySeconds: 30
            timeoutSeconds: 25

这是我遇到的错误(尝试添加一个大的 initialDelay 并尝试添加一个 startupProbe。两者都没有工作)

Liveness probe failed: Get http://x.x.x.x:8080/actuator/health: dial tcp x.x.x.x:8080: connect: connection refused

但是,我可以通过此端点从不同的 pod 获得 200 个响应,这些 pod 位于同一个 ec2 实例和不同的 ec2 实例中。

$k exec -it pod/test sh
# curl http://x.x.x.x:8080/actuator/health  -I
HTTP/1.1 200 OK
Connection: keep-alive
Transfer-Encoding: chunked
Content-Type: application/vnd.spring-boot.actuator.v3+json
correlation-id: x-x-x-x-x
Date: Fri, 09 Oct 2020 14:04:56 GMT

如果没有 liveness probe,应用程序运行良好,我可以通过端口 8080 访问所有端点。

尝试将 livenessprobe 设置为 nginx 图像,它工作正常(因此排除网络问题)

Containers:
  liveness:
    Container ID:   docker://0af63462845d6a2b44490308147c73277d22aff56f993ca7c065a495ff97fcfa
    Image:          nginx
    Image ID:       docker-pullable://nginx@sha256:c628b67d21744fce822d22fdcc0389f6bd763daac23a6b77147d0712ea7102d0
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Tue, 29 Sep 2020 15:53:17 +0530
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:80/ delay=2s timeout=1s period=2s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-57smz (ro)
4

0 回答 0