Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-3450

Implement "Readyness" and "Liveness" endpoints for the CloudBased FlowManager

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Following the discussion at this week's architecture meeting at https://pad.gpii.net/p/arch-2018-10-10-x5154nz1 , the ops team explained that it was desirable to have easy access to GET-driven endpoints on the CloudBased FlowManager in order that Kubernetes could assess it for conditions of Readyness and Liveness - these are defined here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#define-a-liveness-http-request

      In practice the readiness endpoint can simply be an simple endpoint that returns a static payload since our server is live at the point the HTTP listener starts up.

      The liveness probe should make some kind of substantive check of the system's dependencies, most importantly its database connection.

        Attachments

          Activity

            People

            Assignee:
            cli@ocad.ca Cindy Qi Li
            Reporter:
            amb26 Antranig Basman
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: