In AMQ7.10 the pod is not reflecting the livenessprobe set in the ActiveMQArtemis CR

Solution Verified - Updated -

Issue

Set the ActiveMQArtemis CR as follows:

    livenessProbe:
      initialDelaySeconds: 60
      periodSeconds: 20
    readinessProbe:
      initialDelaySeconds: 60
      periodSeconds: 20

But the Operator ignores the settings and based on the output from the StatefulSet:

          livenessProbe:
            tcpSocket:
              port: 8161
            timeoutSeconds: 1
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3

         readinessProbe:
            exec:
              command:
                - /bin/bash
                - '-c'
                - /opt/amq/bin/readinessProbe.sh
            timeoutSeconds: 1
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3

oc get ActiveMQArtemis xxx -oyaml

    readinessProbe: {}
    livenessProbe: {}

So, the livenessProbe setting is ignored by the Operator.

Environment

Red Hat AMQ 7.10
OpenShift 4.10+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content