Description of Problem

• OpenShift GitOps v1.16.2 missing on RHOCP v4.19.2

Additional Info

• Slack thread: https://redhat-internal.slack.com/archives/CMP95ST2N/p1753812450654469 
  Siddhesh Ghadi  Today at 8:47 AM

Yes, 1.16.2 is missing on OCP 4.19. CPASS handles things differently, it releases to all supported OCP versions by default. But with Konflux, we have control over which OCP versions we target for each release. Since 1.16 was supported only up to OCP 4.18, I had assumed CPASS had also limited it to 4.18. However, @Varsha later pointed out that wasn't the case. We did consider re-releasing it for 4.19, but since 1.16 isn't actually supported on 4.19, we deprioritized it.

Problem Reproduction

• Install RHOCP v4.19.2, Check Operator OpenShift GitOps 4.16.2 is missing 

Reproducibility

• Always

Prerequisites/Environment

• RHOCP 4.19.x

Steps to Reproduce

• Install RHOCP v4.19.2, Check Operator OpenShift GitOps 4.16.2 is missing 

Expected Results

• v1.16.2 available to install

Actual Results

• v1.16.1 is available to install

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• None

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.