Feature Overview

Enhance the existing precheck command done in OCPSTRAT-2121 to include comprehensive operator and extension validation checks before platform upgrades, providing a unified pre-upgrade assessment for both platform and extension components.

Goals (This is part of OCP.Next MVP )

• UI Requirements:

• • Console integration showing precheck results in visual format
  • Color-coded severity indicators for identified issues
  • Expandable details for each check category
  • Direct links to operator documentation and remediation steps
  • Progress indicators for running precheck validations
  • Enable precheck UI component to validate operator/extension compatibility with target OpenShift version

• 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

Requirements:

Operator Lifecycle and Support Status Checks:

• Verify End-of-Life (EOL) status for all installed operators
• Check remaining support lifecycle time for each extension
• Identify operators approaching end of support within upgrade window
• Validate operator certification status for target platform version

Operator Compatibility Assessment:

• Check operator platform compatibility matrix against target upgrade version
• Identify required operator updates that must complete before platform upgrade
• Detect operator version conflicts with target platform version
• Verify operator API compatibility with target Kubernetes version

Update Policy and Channel Verification:

• Report current update policy status (manual vs automatic) for all operators
• Identify operators on deprecated or unsupported channels
• Check for available operator updates in current channels
• Validate update path availability to compatible versions

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 OLM-managed operators
• Verify operator pod readiness and resource availability
• Check for operator-specific alerts or degraded conditions

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):

• No API (engineering opinion needed)
• Helm-based deployments
• Automated issue resolution
• Non-OLM managed workloads
• Direct operator upgrade execution

Documentation Considerations:

• Document operator precheck interpretation guide