0

我已经配置了一个 spring-boot pod 并配置了liveness和readiness探针。当我启动 pod 时，describe命令显示以下输出。

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  92s                default-scheduler  Successfully assigned pradeep-ns/order-microservice-rs-8tqrv to pool-h4jq5h014-ukl3l
  Normal   Pulled     43s (x2 over 91s)  kubelet            Container image "classpathio/order-microservice:latest" already present on machine
  Normal   Created    43s (x2 over 91s)  kubelet            Created container order-microservice
  Normal   Started    43s (x2 over 91s)  kubelet            Started container order-microservice
  Warning  Unhealthy  12s (x6 over 72s)  kubelet            Liveness probe failed: Get "http://10.244.0.206:8222/actuator/health/liveness": dial tcp 10.244.0.206:8222: connect: connection refused
  Normal   Killing    12s (x2 over 52s)  kubelet            Container order-microservice failed liveness probe, will be restarted
  Warning  Unhealthy  2s (x8 over 72s)   kubelet            Readiness probe failed: Get "http://10.244.0.206:8222/actuator/health/readiness": dial tcp 10.244.0.206:8222: connect: connection refused

pod定义如下

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: order-microservice-rs
  labels:
    app: order-microservice
spec:
  replicas: 1
  selector:
    matchLabels:
      app: order-microservice
  template:
    metadata:
      name: order-microservice
      labels:
        app: order-microservice
    spec:
      containers:
        - name: order-microservice
          image: classpathio/order-microservice:latest
          imagePullPolicy: IfNotPresent
          env:
            - name: SPRING_PROFILES_ACTIVE
              value: dev
            - name: SPRING_DATASOURCE_USERNAME
              valueFrom:
                secretKeyRef:
                  key: username
                  name: db-credentials
            - name: SPRING_DATASOURCE_PASSWORD
              valueFrom:
                secretKeyRef:
                  key: password
                  name: db-credentials
          volumeMounts:
            - name: app-config
              mountPath: /app/config
            - name: app-logs
              mountPath: /var/log
          livenessProbe:
            httpGet:
              port: 8222
              path: /actuator/health/liveness
            initialDelaySeconds: 10
            periodSeconds: 10
          readinessProbe:
            httpGet:
              port: 8222
              path: /actuator/health/readiness
            initialDelaySeconds: 10
            periodSeconds: 10
          resources:
            requests:
              memory: "550Mi"
              cpu: "500m"
            limits:
              memory: "550Mi"
              cpu: "750m"
      volumes:
        - name: app-config
          configMap:
            name: order-microservice-config
        - name: app-logs
          emptyDir: {}
      restartPolicy: Always

如果我在清单中禁用livenessandreadiness探测并进入 pod，我会在调用和端点时得到有效响应。使用 Kubernetes调用和端点时，为什么我的 pod 会重新启动并失败。我哪里错了？replica-setexechttp://localhost:8222/actuator/health/livenesshttp://localhost:8222/actuator/health/readinessreadinessliveness

更新 如果我删除该resource部分，则 pod 正在运行，但添加resource参数时，probes它们将失败。

4

3 回答 3

2

当您将容器/spring 应用程序限制为 0.5 核（500 毫核）时，启动可能需要比给定的活动探测阈值更长的时间。

您可以增加它们，或者使用具有更宽松设置的 startupProbe（fe failureThreshold 10）。在这种情况下，您可以减少 liveness 探测的时间，并在检测到容器启动成功后获得更快的反馈。

于 2022-02-02T15:41:31.257 回答
1

您的 pod 配置仅提供 0.5 核 CPU，并且您的检查时间太短。根据您的服务器 CPU 性能，spring boot 启动可能需要 10 秒以上的时间。这是我对 spring boot pod 的配置，可能会给你一个点。

"livenessProbe": {
              "httpGet": {
                "path": "/actuator/liveness",
                "port": 11032,
                "scheme": "HTTP"
              },
              "initialDelaySeconds": 90,
              "timeoutSeconds": 30,
              "periodSeconds": 30,
              "successThreshold": 1,
              "failureThreshold": 3
            },
            "readinessProbe": {
              "httpGet": {
                "path": "/actuator/health",
                "port": 11032,
                "scheme": "HTTP"
              },
              "initialDelaySeconds": 60,
              "timeoutSeconds": 30,
              "periodSeconds": 30,
              "successThreshold": 1,
              "failureThreshold": 3
            },

而且我没有限制CPU和内存资源，如果你限制了CPU，它会花费更多的时间。跳这可以帮助你。

于 2022-02-02T16:05:42.380 回答
0

当您尝试针对您的localhost. Kubelet 是一个节点代理，因此请求将发送到您的eth0或等效的，而不是您的localhost.

您可以通过从另一个 pod 向您的 pod 的 IP 地址或备份它的服务发出请求来检查它。

可能您正在使您的应用程序在其上提供服务localhost，而您必须使其在上提供服务0.0.0.0，或者eth0。

于 2022-02-02T16:27:31.930 回答