Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5089

Leverage Operator Subscription Channels to Stop Breaking Existing Deployments

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • Operator
    • None
    • False
    • False
    • Undefined
    • 2021 Week 37-39 (from Sep 13), 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15), 2021 Week 49-51 (from Dec 6th), 2022 Week 02-04 (from Jan 10), 2022 Week 05-07 (from Jan 31)

      Currently the operator offers a 1.x and an alpha channel as options to install Kogito (both of which point to 1.6).

      It would be great if Kogito offered additional channels to help control the update cycle when breaking changes are introduced.

      For example, instead of a 1.x channel, offer more version specific channels:

      1.6.x
      1.5.x
      1.4.x
      etc

      If only a single channel is offered, the operator should not introduce a breaking change such as dropping support for kafka.strimzi.io/v1beta1 or introducing changes that require changes to a runtime codebase.

          1.
          		 Define release stratergy for community Kogito operator Sub-task Closed Major Vaibhav Jain
          2.
          		 Make changes in community Kogito operator release pipeline to channels Sub-task Closed Major Vaibhav Jain
          3.
          		 Define release stratergy for RHPAM Kogito operator Sub-task Closed Major Vaibhav Jain
          4.
          		 Make changes in RHPAM Kogito operator release pipeline to use channels Sub-task Closed Major Vaibhav Jain

              vajain Vaibhav Jain
              troyer@redhat.com Trevor Royer
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: