Goals

• Release Cluster Logging 5.0, independent of OpenShift release cycle.
• Provide Channels as described in Cluster Logging Versions
  • stable and 5.0 channels containing 5.0.0 release.
• Release logging 5.0 to customers via stable and 5.0 channels
• Release logging 5.0.1 with bug fixes via stable and 5.0 channels

Non-Goals

• This epic describes the minimum requirements for a 5.0 release. The tech-preview release of 5.1-beta1 with CloudWatch is covered in other issues.

Motivation

Separate logging from the OCP release lifecycle so we have flexibility to plan releases around features demanded by our customers. Stop testing on OCP daily builds (and breakages.) Improve CI turn-around by gating logging changes on logging tests only. Release tech-preview features on a tech-preview channel.

Acceptance Criteria

• CPaas configured and tested to build channels stable and 5.0 the 5.0 release branch.
• Upgrade testing to validate correct upgrade from 4.4, 4.5, and 4.6 in running system (is this required/sufficient?)
• Test process for releasing 5.0.1 z-stream update on stable and 5.0 channels
• UI testing for installation/upgrade using 5.0 and stable channels.
• Must be easy to navigate for a user familiar with the 4.6 install/upgrade experience
• Installation guide

Documentation Considerations

• Introduce meaning of channels.
• Update any installation/upgrade specific information to use our new channels.
• Introduce release notes section.
• Introduce section that explains the version support between Logging Operator and Elasticsearch Operator.

Dependencies (internal and external)

• CPaas build, nearing completion.
• OSD able to accept release candidate via Add-On flow.

Previous Work (Optional):

• CPaaS
• Cluster Logging Versions

Open questions:

• How to build multi-version channels?
• How to prevent/warn about unsupported OCP/Logging version combinations?
• How to prevent/manage upgrades from tech-preview beta versions to GA versions?