Uploaded image for project: 'Nuxeo ECM Build/Test Environment'
  1. Nuxeo ECM Build/Test Environment
  2. NXBT-3512

[Platform CI] Make Jenkins benefit from the startup probe

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Continuous Integration

      Description

      Since Kubernetes 1.18, a startup probe is available to handle containers with a long startup time, see https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes.

      The cluster was recently upgraded to v1.18.17-gke.700, thus, the startup probe is now available, as we can see: 

      k describe pod jenkins-0
...
  Warning  Unhealthy  16m                kubelet            Startup probe failed: Get http://10.60.53.14:8080/login: dial tcp 10.60.53.14:8080: connect: connection refused
  Warning  Unhealthy  16m                kubelet            Startup probe failed: Get http://10.60.53.14:8080/login: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  15m (x5 over 16m)  kubelet            Startup probe failed: HTTP probe failed with statuscode: 503

      Let's remove the now useless initialDelaySeconds: 60 from the livenessProbe and readinessProbe.

        Attachments

          Issue Links

          Is referenced in

          [Captain Hook] PR for master: #7 PR for master: #7

            Activity

              People

              • Assignee:
                ataillefer Antoine Taillefer
                Reporter:
                ataillefer Antoine Taillefer
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: