Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Done
Priority: Critical
Fix Version/s: 1.5.0
Affects Version/s: None
Component/s: Productization
Labels:
- release-note-item
- rn-done-resolved

Story Points:
3
Blocked:
False
Ready:
False
Release Note Text:

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.

Sprint:
GITOPS Sprint 215

SFDC Cases Counter:
SFDC Cases Links:

Description

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