Feature Overview (aka. Goal Summary)  

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

Goals

• Nightly builds of leading edge OCP (OKD.next) against Kube main as an early signal of API incompatibilities to serve both the Kube community and OCP release readiness
• Frequent regression testing
• Reduction in OCP carry patches

Requirements (aka. Acceptance Criteria):

• Nightly rebase of OKD.next against Kube main
• A roadmap for improving the release pipeline.

Background

Currently we rebase Kube once per release, resulting in failures that are difficult to trace back to their origin. Nightly testing will give OCP and Kube an improved readiness signal and create a log where it will be easier to identify regressions in the future.