Feature Overview

See OCPSTRAT-2618

Goals

See OCPSTRAT-2618

Requirements - Phase 2:

A structured extension update workflow that covers single-step and multi-step update flows in two stages:

Preview & Preflight checks:

• Aggregated from all versions along the update path: release notes, change previews (operator-related Kubernetes resources, specifically permissions) and compatibility assessments provided by the extension author
• Ability to launch and review preflight checks that are optionally provided by the future operator versions, such as custom alerting rules or custom logic
• Ability to launch the upgrade for one or more selected operators

Update status:

• Insights into the upgrade process of each operator updating, including overall progress percentage and any in-between updates along a multi-step upgrade path
• Custom upgrade status conditions optionally relayed by the operator

All information should be accessible via APIs for use in Cluster Console, CLIs, and ACM.

Use Cases:

• A platform engineer reviews all compatibility assessments of a multi-step operator upgrade to determine the overall impact and changes to be expected as part of this update
• A platform engineer discovers the availability of preflight checks provided by the future version(s) of the operators and runs them to determine any known blockers for a successful update; they can proceed with the update regardless of the preflight check outcome
• A platform engineering reviews the progress after they launched the update and discovers which steps of the multi-step upgrade flow have already been completed and if there were any warnings or other status outputs

Out of Scope

For now: Helm

Background

Read the full proposal here: https://docs.google.com/document/d/1MzGGov5slwnEmohoW4ZSVvhxSiaBXRlWjSzoO3affMY/edit?tab=t.mepx4xanj5dv 

Interoperability Considerations

This experience must be available without degradation in disconnected environments lacking direct internet access and AI capabilities.