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

[Operator] ActiveMQArtemis custom labels are not propagated to PODs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • operator
    • None
    • False
    • False
    • Hide

      Define an ActiveMQArtemis CR with your own labels:

       

        apiVersion: broker.amq.io/v2alpha5
  kind: ActiveMQArtemis
  metadata:
    labels:
      ActiveMQArtemis: my-amq7-deployment
      mylabel1: value1
      mylabel2: value2
  spec:
    adminUser: adminuser
    deploymentPlan:
      size: 2
  :
  :
  :

       

       

      Apply the CustomResource and check the StatefulSet and PODs labels: neither STS nor PODs are labeled with mylabel1 and mylabel2. The only propagated label is ActiveMQArtemis.

       

      Show
      Define an ActiveMQArtemis CR with your own labels:   apiVersion: broker.amq.io/v2alpha5   kind: ActiveMQArtemis   metadata:     labels:       ActiveMQArtemis: my-amq7-deployment mylabel1: value1 mylabel2: value2 spec:     adminUser: adminuser     deploymentPlan:       size: 2 : : :     Apply the CustomResource and check the StatefulSet and PODs labels: neither STS nor PODs are labeled with mylabel1 and mylabel2 . The only propagated label is ActiveMQArtemis .  

      When you apply an ActiveMQArtemis custom resource and you have defined some custom labels and values (because you might need them for any purpose), those labels are not propagated to the StatefulSet (therefore every POD running in the AMQ cluster is not labeled with the desired labels, either).

      All labels configured explicitly in the custom resource should be (at least) propagated to every running POD. But perhaps it would be even better to propagate them to all resources created by the Operator (such as PVCs, secrets, Configmaps...).

            rh-ee-ataylor Andy Taylor
            ryanezil Rafael Yáñez Illescas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: