Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-4210

Wrong probe configuration for Quarkus deployments

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.3.0.Final
    • 1.1.0.Final
    • Operator
    • None
    • False
    • False
    • Undefined
    • Hide

      Deploy example https://github.com/kiegroup/kogito-cloud-operator/blob/master/examples/process-quarkus-example.yaml on OCP
      Check readiness and liveness probes
      =>
      expected - probes are watching deployment using httpGet configuration with "/health/live" and "/health/ready" paths
      actual - probes are watching deployment using tcpSocket port 8080.

      Show
      Deploy example https://github.com/kiegroup/kogito-cloud-operator/blob/master/examples/process-quarkus-example.yaml on OCP Check readiness and liveness probes => expected - probes are watching deployment using httpGet configuration with "/health/live" and "/health/ready" paths actual - probes are watching deployment using tcpSocket port 8080.
    • ---
    • ---
    • 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15)

    Description

      If Quarkus application is deployed on OpenShift the Kogito operator creates a readiness and liveness probes watching tcpSocket port 8080.
      However expected behaviour is to watch "/health/live" and "/health/ready" paths of deployed application.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-4279 Adjust Kogito runtime probes based on health endpoint availability

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. KOGITO-4173 Adjust the default probe and metrics URL for Quarkus

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kevin-mok Kevin Mok (Inactive)
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: