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

      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.

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

              Created:
              Updated:
              Resolved: