Add Gitlab Operator Bundle to OCP 4.13 OperatorHub

Summary

Version 0.23.1 of the operator doesn't show up in the OCP 4.13 (ROSA) operator hub.

Current behavior

Only gitlab operator 0.19.0 which says was built 2 years ago is available.

Expected behavior

Expecting to see the latest operator 0.23.1 to show as it says that it's released for 4.13 in the redhead marketplace.

What current appears to be blocking this from appearing in the OperatorHub is the OPENSHIFT_MAX=${OPENSHIFT_MAX:-"4.12"} var not being updated to 4.13 in the file /Users/chlong/foss_contributions/gitlab-operator/redhat/operator-certification/scripts/configure_bundle.sh

I can make a MR for this if you like. I must add that it's not a good look to see that you have approx. 20+ version releases in the RH catalog page but we can only install a 2 year old release in OCP 4.13 ROSA.

Versions

• Operator: 0.19.0 should be 0.23.1
• Platform:
  • Cloud: ROSA version 4.13.8
• Kubernetes: (kubectl version)
  • Client Version: v1.26.1
  • Kustomize Version: v4.5.7
  • Server Version: v1.26.6+73ac561

Thanks @clong4, this will be completed along with #1270 (closed) when we have fully tested the Operator against 4.13 in CI so we can identify any changes that need to be made

added For Scheduling devopssystems groupdistribution maintenancepipelines priority2 sectioncore platform typemaintenance labels

added to epic gitlab-org&10785 (closed)

Only gitlab operator 0.19.0 which says was built 2 years ago is available.

This is a known issue, being tracked in #1314 (closed).

marked this issue as blocked by #1270 (closed)

removed For Scheduling label

added Deliverable label

changed milestone to %16.9

mentioned in issue gitlab-org/quality/triage-reports#15691 (closed)

Current bundles should have max and min OCP version set and older ones were patched in https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/3503.

Closing this. Feel free to reopen if you're still having issues.

closed