No broker after upgrading to operator 1.2.1

[lnthai2002]

Hello,
We have recently upgraded to artemis operator 1.2.1 and we noticed that the broker pod does not spawn anymore. I dont see any error in the operator controller, the ActiveMqArtemis resource is created in the watch namespace but there is artemis statefulset created. When i describe the ActiveMqArtemis resource in the watched namespace, i noticed this:

I'm not sure why it complain about ingress. How can i get more info about the invalid ingress setting?

[lnthai2002]

here is my def for the ActiveMqArtemis

apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: activemq-artemis-broker
spec:
  acceptors:
    - name: "all-protocols-acceptor"
      bindToAllInterfaces: true
      port: 61617
#      protocols: "CORE" # not defining protocols make broker enable all protocols (CORE,STOMP, AMQP,...) support
  addressSettings:
    applyRule: merge_all
    addressSetting:
    - match: '#'
      deadLetterAddress: DLQ
      expiryAddress: ExpiryQueue
      redistributionDelay: 60000
      redeliveryDelay: 0
      maxSizeBytes: "-1"
      messageCounterHistoryDayLimit: 10
      addressFullPolicy: PAGE
      autoCreateQueues: true
      autoCreateAddresses: true
      autoCreateJmsQueues: true
      autoCreateJmsTopics: true
      autoDeleteQueues: false
      autoDeleteCreatedQueues: false
      autoDeleteAddresses: false
      defaultConsumerWindowSize: 0
    - match: 'JOB_QUEUE.#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: 0
      autoDeleteAddresses: true
    - match: 'CRON_JOB_QUEUE.#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: 0
      autoDeleteAddresses: true
    - match: 'QUEUE.#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: 0
      autoDeleteAddresses: true
    - match: 'TOPIC.#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: 0
      autoDeleteAddresses: true
    - match: 'TOPIC.internal.#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete to avoid delete due to temporary lost connection
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: -1
      autoDeleteAddresses: true
    - match: 'TOPIC.retro.#'
      retroactiveMessageCount: 1
      autoDeleteQueues: true
      autoDeleteQueuesDelay: 0
      autoDeleteQueuesMessageCount: -1
    - match: '$.artemis.internal.#'
      autoDeleteQueues: false
      autoDeleteAddresses: true
    - match: 'internal-ncp-deployment'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: -1
      autoDeleteAddresses: true
    - match: 'internal-cs-log-level-#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: -1
      autoDeleteAddresses: true
    - match: 'internal_core_service_interruption-#'
      autoDeleteQueues: true
      autoDeleteCreatedQueues: true
# wait 5 MIN before delete queues
      autoDeleteQueuesDelay: 300000
      autoDeleteQueuesMessageCount: -1
      autoDeleteAddresses: true
  console:
    expose: true
    sslEnabled: false
  deploymentPlan:
    size: {{ .Values.replicas }}
    livenessProbe:
      initialDelaySeconds: 60
      periodSeconds: 10
      timeoutSeconds: 30
    readinessProbe:
      initialDelaySeconds: 60
      periodSeconds: 10
      timeoutSeconds: 30
    requireLogin: true
    messageMigration: true
    persistenceEnabled: {{ .Values.persistence.enabled }}
    {{- if .Values.persistence.enabled }}
    podSecurityContext:
      fsGroup: 0
    storage:
      size: {{ .Values.persistence.size }}
      storageClassName: {{ .Values.persistence.storageClass }}
    {{- end }}
    resources:
      requests:
        cpu: {{ .Values.resources.requests.cpu }}
        memory: {{ .Values.resources.requests.memory }}
  adminUser: {{ .Values.artemisUser }}
  adminPassword: {{ .Values.artemisPassword }}

[brusdev]

@lnthai2002 by default, the expose mode is ingress on Kubernetes and in your CR the field spec.console.expose is true. This issue is expected because since 1.2.0 the operator fails the validation for the acceptors, connectors and console exposed with the ingress mode when both ingress domain and ingress host are not specified, for further details see #828.

You can fix this issue setting the field spec.console.expose to false or setting a value for the field spec.console.ingressHost or setting a value for the field spec.ingressDomain, i.e.

spec:
  ingressDomain: 'my-org.com'

[lnthai2002]

Thanks for the suggestion. I am not interested in accessing web console from outside kube network. However, I have an application running on a different namespace that need to send request to jolokia endpoints (hosted inside web console by default). The app send request to http://activemq-artemis-broker-wconsj-0-svc.mynamespace.svc.cluster.local:8161. If I set spec.console.expose=false, would my app still be able to access the jolokia endpoints?

[brusdev]

Yes, the services are created also when expose is false.

UPDATE
My previous answer is partially wrong because only the headless and the ping services are created when expose is false so in this case your app should send requests to http://activemq-artemis-broker-ss-0.activemq-artemis-broker-hdls-svc.mynamespace.svc.cluster.local:8161/

[lnthai2002]

Thank you