Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-4528

[PROD] Update OLM channels of Streams 2.2.x to avoid bundle channel collision

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None

      Now that we support two AMQ Streams releases at the same time which are installable via OLM, we must employ the "fancy channeling" technique on our released bundle channels as described in the post mortem document here [1]

      Basically, once Streams 2.3.0 is released, we cannot ship Streams 2.2.x releases to the `stable`and `amq-streams-2.x` channels anymore because they would have a lower semver than what is at the head of those channels.

       

      For this task we must remove `stable`, `amq-streams-2.x` channels from here so[1] that the line reads like this:

        operators.operatorframework.io.bundle.channels.v1: amq-streams-2.2.x 

       

      [1] https://docs.google.com/document/d/1orhy1XnVJrECt2NCpl8Y0_m9Xj58MsBdGhkRwyH7qGI/edit

      [2] https://github.com/jboss-container-images/amqstreams-1-openshift-image/blob/amqstreams23-dev/operator-metadata/metadata/annotations.yaml#L4

              rh-ee-ocorriga Owen Corrigan
              kliberti Kyle Liberti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: