Feature Overview

Continuing on the user experience delivered by the cluster-version-specific preflight check framework in OCPSTRAT-2815, we aim to include comprehensive operator-version specific validation checks before operator upgrades, increasing customer confidence and update success for OLM-managed operators. This also provides the foundation for a unified pre-upgrade assessment for both platform and extension components, driven by a UI.

Goals 

OLM & Catalog Framework

• design a generic catalog-based packaging and delivery vehicle for Operator-version specific preflight check definitions
• design a generic API for operators to run Operator-version specific preflight checks that is separate from the operation to update the operator to the desired target version

UI Requirements:

• integrate this into OLM update planner UI (OCPSTRAT-2620) showing precheck results in visual format
• integrate this into the cluster upgrade dashboard (OCPSTRAT-2763)

CLI Requirements:

• Enable precheck command to validate operator/extension compatibility with target OpenShift version
• Identify operators that require updates before platform upgrade can proceed
• Surface operator-specific upgrade blockers alongside platform checks
• Provide clear guidance on operator update sequencing relative to platform upgrades
• Structured JSON output option for programmatic consumption

Ideas for pre-checks conducted by operators:

Dependency and Interoperability Checks:

• Identify operator interdependencies that could block upgrades
• Check for breaking changes in operator APIs used by other operators
• Validate CRD version compatibility across dependent operators
• Detect potential conflicts between operator upgrade sequences

Extension-Specific Health Validation:

• Check health status of all operator components
• Check health status of all operands
• Verify resource availability

Change Impact Analysis:

• Preview breaking changes in operator updates required for platform upgrade
• Identify deprecated operator features that will be removed
• Check for required configuration changes post-upgrade
• Assess workload disruption from operator updates

Out of Scope (Remains Unchanged):

• Automated issue resolution
• Non-OLM managed workloads

Documentation Considerations:

• Document operator precheck interpretation guide