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

Add new ActiveMQArtemis CRD version to reflect actual configuration schema

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • 7.5.0.CR1
    • None
    • operator
    • None
    • AMQ Sprint 3219, AMQ Broker 2919, AMQ Sprint 3519

    Description

      At the moment we have a number of items in our v1alpha1 ActiveMQArtemis CRD, the names of which do not necessarily reflect how they are defined in the actual artemis-configuration schema

      This should be rectified, so that further configuration items can be added and a consistent end user experience is the result between standalone and on OpenShift.

      Note also that as a result of the move from v1alpha1 to v2alpha1 the scaledown controller is no longer explicitly deployed via Custom Resource Definition/Custom Resource but rather a new field entitled 'messageMigration'

      Attachments

        Issue Links

          is duplicated by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-2162 [AMQ7] Provide option to define additional properties in broker.xml

          • 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
          is related to

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-2762 Update OLM yaml to utilize new v2alpha1 CRD

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-2514 Provide way for custom broker.xml in the container image

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

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-2763 Allow web console configuration from the v2alpha1 CRD

          • 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

          Activity

            People

              rhn-support-rkieley Roderick Kieley
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: