-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
Konflux for ClusterLogging
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
KONFLUX-209 - OpenShift Logging Enablement
-
NEW
-
75% To Do, 25% In Progress, 0% Done
-
Release Note Not Required
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.2 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
- An official, 6.2 release of Red Hat OpenShift Logging that meets release engineering requirements
- Documented workflow identifying how development, QE, and documentation work together
- Documented understanding of releasing and advisory and how it is published
Risk and Assumptions
The 6.2 release is targeted for Q1 to co-inside with OCP release (4.18?) . This release has been expressed as having limited capacity to move. It is possible we do not have all the configuration and changes in place to release via Konflux. It may be necessary for us to temporarily revert to CPaaS which means we need ~3 weeks to ensure we are set and ready to move forward. We need to make a determination mid-Feb '25.
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?