Feature Overview

Enable direct, skip-level updates (e.g., N to N+2 or N+3) for OpenShift Extended Update Support (EUS) customers, allowing them to perform only one update for every three they currently execute and simplifying their EUS-to-EUS upgrade path.

Goals (aka. expected user outcomes)

The cluster administrator persona will be able to perform an Upgrade directly from version N to N+X (e.g., 4.12 to 4.15) while maintaining compatibility and safety.

Requirements (aka. Acceptance Criteria):   

• The new Design and implementation must utilize KEP-4330 to enable 2-stage upgrades for skip-level paths
• The CVO and Cincinnati/Update Service must be enhanced to support and recommend multi-path, skip-level update graphs (e.g., N to N+3).
• The full OpenShift ecosystem, including all core and partner operators, must be emulation-aware and compatible with the skip-level process

Out of Scope

• Exposing "emulation modes" as a permanent production feature for customers to manage.
• Skip-level updates that exceed the guaranteed compatibility range (N to N-3).
• Rollback is out of scope. And will be looked in the future.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.