Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-1791

Adopt versioned channel schemes

XMLWordPrintable

    • 3
    • False
    • False
    • Hide
      With this update, the latest releases of the Red Hat OpenShift GitOps are available in latest and version-based channels. To get these upgrades, update the channel parameter in the Subscription object YAML file: change its value from stable to latest or a version-based channel such as gitops-1.6.
      Show
      With this update, the latest releases of the Red Hat OpenShift GitOps are available in latest and version-based channels. To get these upgrades, update the channel parameter in the Subscription object YAML file: change its value from stable to latest or a version-based channel such as gitops-1.6.
    • GITOPS Sprint 215

      Why

      We currently always publish new releases to both stable and preview channels. Therefore, users have opted for auto upgrade will not be able to stay in one minor release. For example, users with auto update enabled will get upgrade from 1.3.4 to 1.4.0.  The works fine when we only have to support N-1.  It does not work well when we are supporting N-2. Users cannot stay at 1.3 when 1.4.0 is out with auto update is enabled.

      What

      We need to adopt some channel publishing strategy that allow users to continue getting z-stream fixes (auto update) while staying at an old supported minor release.

      Acceptance Criteria

        1. image-2022-03-28-16-59-21-535.png
          image-2022-03-28-16-59-21-535.png
          18 kB
        2. image-2022-03-28-17-01-08-329.png
          image-2022-03-28-17-01-08-329.png
          18 kB
        3. image-2022-03-28-17-04-28-253.png
          image-2022-03-28-17-04-28-253.png
          11 kB
        4. image-2022-03-29-10-45-52-619.png
          image-2022-03-29-10-45-52-619.png
          35 kB

              jpitman63 John Pitman
              wtam_at_redhat William Tam
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: