Epic Goal

Expose the preflight functionality being developed in OTA-253 and OTA-1793 as part of the standalone cluster's update experience. Possibly as part of OCPSTRAT-2763's work on overhauling the in-cluster web-console update experience.

Why is this important?

Requesting an update can be a stressful experience, and hearing about compatibility issues on the day you'd been hoping to update doesn't give you much time to resolve those issues. By exposing the ability to request preflights in the web-console, we make the functionality more accessible, and increase the likelihood that cluster-admins run low-stakes preflight checks well in advance of their planned update, and again as they close in on their planned launch time, to help them be more confident when they do launch the update request.

Scenarios

As a cluster-admin considering an update, I can launch preflight checks

On stand-alone clusters (HyperShift is out of scope for now). For any release in availableUpdates or conditionalUpdates; there is no need for the console to allow prechecks of arbitrary release image pullspecs.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies

Depends on OTA-253 delivering a feature gate slug and tech-preview functionality. Waiting until OTA-1793 may be possible, depending on how quickly that happens and business goals for console support.

Previous Work

OCPSTRAT-2763 wireframes include some discussion of how preflight checking could be represented in web UIs.

Open questions

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>