Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-6156

Konflux Pipeline Service Health Endpoint

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Konflux Pipeline Service Health Endpoint
    • False
    • None
    • False
    • To Do
    • KONFLUX-4841 - Composite system availability metric - phase 3

      [T-shirt sized: XL]

      Epic Goal

      • Discuss with the team what does it mean for our component to be up.
      • Propose changes to OSP so that the operator status reflects the service's availability
      • Create and deploy an HTTP Service that queries that availability

      Why is this important?

      • The Service will be used to determine Konflux overall uptime.

      Scenarios

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      1. Where do we draw the line to flag our service as down? 

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • Support and SRE teams are provided with enough skills to support the feature in production environment

            vdemeest Vincent Demeester
            nhaklik@redhat.com Norbert Haklik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: