Publish Operator 2.6.2

Summary

This issue will serve as a checklist and record of releases for GitLab Operator 2.6.2.

Much of the process is automated by release-tools.

To do

1. Confirm that publish jobs in the tag pipeline in Canonical repo has completed.
2. Confirm that the Release has been created with the correct content in the tag message and Release description..
3. OLM bundle testing has been completed
4. Release to OperatorHub.io catalog
5. Release to RedHat community catalog
6. Release to RedHat certified catalog

Use the publish.sh script to release to the OLM catalogs:

# Use skip mode if new release adds support for a new OCP minor.
export OLM_SKIP_VERSION="2.6.2"

# Use replaced mode for releases with unchanged OCP support.
export PREVIOUS_OPERATOR_VERSION="2.6.2" 

scripts/tools/publish.sh VERSION [TARGETS]

This scripts checks the requirements and submits the Operator to all three targets. You can limit the scope of the release by passing one or more targets. Use:

• operatorhub for OperatorHub.io
• redhat-community for RedHat community catalog
• redhat-marketplace for RedHat certified catalog