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

Support Floating x or x.y version is Artemis CRD version string

    XMLWordPrintable

Details

    Description

      The Version of the Artemis CRD allows a broker version to be specified, in the absence of this being set, the operator picks the latest or current version. When it is present it locks down the version.

      However it would be better if the version could also specify a floating version, like 7 or 7.2 or 7.2.1 and in all cases if the match is within a range (as configured in the operator) the latest in that range is used.

      to lock down, a fully qualified version is required and only cve upgrades will be applied when the image tag is updated by the operator csv.  

       

      To lock down:

      Is it easy to specify the fully qualified version? - it is via specifying a spec.image value in the CR. 

       

      OSGI has a very comprehensive mechanism for version ranges in bundles, probably kube does too. We don't want to reinvent a wheel here and we may not need to be two general b/c the operator and bundle will already provide some constraint.

      Attachments

        Issue Links

          impacts account

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7519 [Docs] Support Floating x or x.y version is Artemis CRD version string

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7478 Operator does not honor the upgrades.minor field

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7105 The update of spec.version in ActiveMQArtemis CR doesn't trigger the rolling update strategy

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7878 [LTS] The update of spec.version in ActiveMQArtemis CR doesn't trigger the rolling update strategy

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6776 Operator still does not honor broker version if upgrades are not enabled

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

          Activity

            People

              gaohoward Howard Gao
              gtully@redhat.com Gary Tully
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: