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

Ensure name and label generation works for the multi-statefulset case

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • AMQ 7.9.0.CR1
    • AMQ 7.5.0.GA, 7.5.0.CR3, AMQ 7.6.0.GA, AMQ 7.8.2.OPR.1.GA
    • operator
    • 2
    • Release Notes

    Description

      In updating the broker operator to be able to generate the names of kubernetes objects such as services, secrets, routes, etc. as well as have a singular source of truth for labeling a limitation was inadvertently introduced. The limitation is the result of the fact that the required Namer instances are not used in a namespacedName way unlike the way the finite state machine is used.

      This limitation was somewhat inadvertent and should be addressed.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-3005 Make AMQ Broker Operator (Artemis) to Watch in all Namespaces

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-3400 Doc: [OCP] Ensure name and label generation works for the multi-statefulset case

          • Critical - To be worked on immediately following BLOCKER issues.
          • New
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-1648 Don't hardcode openshift.DNS_PING service name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-4287 Support multiple broker instances in the same namespace

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              gaohoward Howard Gao
              rhn-support-rkieley Roderick Kieley
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: