Feature Overview (aka. Goal Summary)  

OCP needs more frequent and earlier readiness signals of the intersection of OCP with RHEL in order to improve release stability and predictability.

Goals

• Nightly comparative OKD.next/SCOS regression testing informing OCP's next sprintly release.
• Frequent builds of leading edge OCP (OKD.next) against SCOS resulting in identifying opportunities to improve the build pipeline.

Requirements (aka. Acceptance Criteria):

• Sprintly builds of an OKD Stream based on OCP's sprintly .next
• Nightly comparative regression testing
• A roadmap for improving the release pipeline.

Background

OCP 4.13 was released against RHEL9.2 beta. We expect this trend to continue, thus the need for more frequent comparative regression testing to get a better readiness signal earlier.