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

Deployment constantly updates when deployed with custom probes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 1.6.0.Final
    • 1.4.0.Final
    • Operator
    • None
    • False
    • False
    • Undefined
    • 2021 Week 13-15 (from Mar 29)

    Description

      When deploying with the following YAML:

      apiVersion: app.kiegroup.org/v1beta1
      kind: KogitoRuntime
      metadata: 
        name: qe
      spec: 
        replicas: 1
        image: quay.io/kmok/process-quarkus-example
        probes: 
          livenessProbe:      
            httpGet:         
              path: /q/health/live
              port: 8080
            failureThreshold: 10
            periodSeconds: 5
      

      The operator log will continually run and output:

      {"level":"info","ts":1617035637.2587748,"logger":"comparator","msg":"Objects are not equal"...
      

      This causes the deployment to be updated every second. What's causing this issue is a discrepancy between the deployed and requested resources. In the requested resources, the liveness probe is missing the URI scheme for the handler where as the deployed one has "HTTP" for it as the default. In previous tests and while working on KOGITO-4322, the following probe values were also being set to their default values in the deployed resource and causing a discrepancy from the requested where they were not set in the YAML:

      • TimeoutSeconds
      • PeriodSeconds
      • SuccessThreshold
      • FailureThreshold

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: