Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-6872

Using Liveness probe with tcpSocket in the ActiveMQArtemis CR ends with a wrong configuration in the StatefulSet

    XMLWordPrintable

Details

    Description

      Using Liveness probe with tcpSocket in the ActiveMQArtemis CR ends with a wrong configuration in the StatefulSet.

      the tcpSocket property is missing. As a result the StatefulSet doesn't create the pod, because the liveness probe is invalid.

      The yaml:

      apiVersion: broker.amq.io/v1beta1
      kind: ActiveMQArtemis
      metadata:
        name: amq-broker
        namespace: amq
      spec:
        deploymentPlan:
          image: placeholder
          jolokiaAgentEnabled: false
          journalType: nio
          managementRBACEnabled: true
          messageMigration: false
          persistenceEnabled: false
          requireLogin: false
          size: 1
          livenessProbe:
            failureThreshold: 3
            initialDelaySeconds: 60
            periodSeconds: 10
            successThreshold: 1
            tcpSocket:
              port: 8161
            timeoutSeconds: 5
        version: '7.10.0'
      

      ends with the following in the stateful set:

                livenessProbe:
                  initialDelaySeconds: 60
                  timeoutSeconds: 5
                  periodSeconds: 10
                  successThreshold: 1
                  failureThreshold: 3
      

      Attachments

        Activity

          People

            gaohoward Howard Gao
            rhn-support-aboucham Abel Bouchama
            Mikhail Krutov Mikhail Krutov
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: