activemq-artemis-broker-wconsj-0-svc service no longer created

[lnthai2002]

Hi, i just noticed that after upgrading to operator 1.2.1 the kubernetes service activemq-artemis-broker-wconsj-0-svc is no longer created. What do i need to do to to have it created again?

[brusdev]

@lnthai2002 maybe one of the new validation checks is failing. Can you share your ActiveMQArtemis CR or its status?

Execute the following command to dump of a ActiveMQArtemis CR:

kubectl get activemqartemis <CR_NAME> -o yaml

[lnthai2002]

Here is my CR:

apiVersion: v1
items:
- apiVersion: broker.amq.io/v1beta1
  kind: ActiveMQArtemis
  metadata:
    creationTimestamp: "2024-05-02T13:26:01Z"
    generation: 1
    name: activemq-artemis-broker
    namespace: ncp-stack-nle
    resourceVersion: "1624283699"
    uid: ac6923ff-11ab-4236-9a02-f31f6169ecfa
  spec:
    acceptors:
    - bindToAllInterfaces: true
      name: all-protocols-acceptor
      port: 61617
    addressSettings:
      addressSetting:
      - addressFullPolicy: PAGE
        autoCreateAddresses: true
        autoCreateJmsQueues: true
        autoCreateJmsTopics: true
        autoCreateQueues: true
        autoDeleteAddresses: false
        autoDeleteCreatedQueues: false
        autoDeleteQueues: false
        deadLetterAddress: DLQ
        defaultConsumerWindowSize: 0
        expiryAddress: ExpiryQueue
        match: '#'
        maxSizeBytes: "-1"
        messageCounterHistoryDayLimit: 10
        redeliveryDelay: 0
        redistributionDelay: 60000
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: 0
        match: JOB_QUEUE.#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: 0
        match: CRON_JOB_QUEUE.#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: 0
        match: QUEUE.#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: 0
        match: TOPIC.#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: -1
        match: TOPIC.internal.#
      - autoDeleteQueues: true
        autoDeleteQueuesDelay: 0
        autoDeleteQueuesMessageCount: -1
        match: TOPIC.retro.#
        retroactiveMessageCount: 1
      - autoDeleteAddresses: true
        autoDeleteQueues: false
        match: $.artemis.internal.#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: -1
        match: internal-ncp-deployment
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: -1
        match: internal-cs-log-level-#
      - autoDeleteAddresses: true
        autoDeleteCreatedQueues: true
        autoDeleteQueues: true
        autoDeleteQueuesDelay: 300000
        autoDeleteQueuesMessageCount: -1
        match: internal_core_service_interruption-#
      applyRule: merge_all
    adminPassword: blah
    adminUser: blahbah
    console:
      expose: false
      sslEnabled: false
    deploymentPlan:
      labels:
        managedService: "true"
      livenessProbe:
        initialDelaySeconds: 60
        periodSeconds: 10
        timeoutSeconds: 30
      messageMigration: true
      persistenceEnabled: true
      podSecurityContext:
        fsGroup: 0
      readinessProbe:
        initialDelaySeconds: 60
        periodSeconds: 10
        timeoutSeconds: 30
      requireLogin: true
      resources:
        requests:
          cpu: 100m
          memory: 4Gi
      size: 1
      storage:
        size: 20Gi
        storageClassName: gp3-ncp
  status:
    conditions:
    - lastTransitionTime: "2024-05-02T13:26:01Z"
      message: ""
      observedGeneration: 1
      reason: ValidationSucceded
      status: "True"
      type: Valid
    - lastTransitionTime: "2024-05-02T13:28:11Z"
      message: ""
      reason: Applied
      status: "True"
      type: BrokerPropertiesApplied
    - lastTransitionTime: "2024-05-02T13:28:10Z"
      message: ""
      reason: AllPodsReady
      status: "True"
      type: Deployed
    - lastTransitionTime: "2024-05-02T13:28:10Z"
      message: ""
      reason: ResourceReady
      status: "True"
      type: Ready
    - lastTransitionTime: "2024-05-02T13:28:11Z"
      message: ""
      reason: VersionMatch
      status: "True"
      type: BrokerVersionAligned
    deploymentPlanSize: 1
    podStatus:
      ready:
      - activemq-artemis-broker-ss-0
    scaleLabelSelector: ActiveMQArtemis=activemq-artemis-broker,application=activemq-artemis-broker-app,managedService=true
    upgrade:
      majorUpdates: true
      minorUpdates: true
      patchUpdates: true
      securityUpdates: true
    version:
      brokerVersion: 2.33.0
      image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes@sha256:b293c1269166cc6181f68b8d803fdfcf20fdbd5df2787ed0453724b22e298fb2
      initImage: quay.io/artemiscloud/activemq-artemis-broker-init@sha256:93168fd8cd4fb32f041795afb8fb0e21cf81081d6cc463a44356e153dc1ad032
kind: List
metadata:
  resourceVersion: ""

[lnthai2002]

As you can see, the spec.console.expose is false and from #918 I assume the kubernetes service for web console should still be created but it isn't. All i see are these:

[brusdev]

@lnthai2002 sorry that was my fault I misread your question and I have just updated my previous answer.

You can use the pod hostname when console.expose is false, i.e. http://activemq-artemis-broker-ss-0.activemq-artemis-broker-hdls-svc.mynamespace.svc.cluster.local:8161/

[lnthai2002]

Thanks, my bad too, i didnt see hdls also expose 8161