Goals

The goal of this epic is to move the productization of Cluster Logging to Konflux to align with product engineering's mandate.  The initial effort will focus on the 6.3 release of logging, with follow-up efforts to onboard the remaining 6.x release streams.

Non-Goals

Move productization of  logging 5.x to konflux (except maybe 5.9 since it does not include the EO?)

Motivation

Alternatives

There are no alternatives given the intent to sunset CPaaS

Acceptance Criteria

• Official 6.0-6.3 releases of Red Hat OpenShift Logging that meets release engineering requirements
• Verified Z-stream numbering that continues from the last CPaaS z-stream build (i.e. 6.1.8)
• Documented workflow identifying how development, QE, and documentation work together
• Documented understanding of releasing and advisory and how it is published
• Switching between different release channels (stable-6.1, stable-6.2, ...) works as before

Risk and Assumptions

• The risk of being able to push all active releases within a short period of time since all streams MUST move to konflux at the same time
• Moving 5.x to konflux when it only will live to Nov 2025

Documentation Considerations

• Internal documentation for the teams to capture process

Open Questions

• How are FBC images distributed upon release (e.g. individually? combined into "master" like CPaaS)? What conflicts do we need to be aware of while shipping a bundle via CPaaS and a FBC concurrently?
  A: All streams that will exist on a particular OCP version must be part of the same FBC.  There will be no pushing content that is built by both CPAAS and Konflux because this breaks the container grade functionality for customers.  We must move everything

Additional Notes