Publish Operator 1.2.1

Summary

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

Much of the process is automated by release-tools.

To do

1. Bump chart versions on stable and master branch
   1. Bump Charts to 8.2.1, 8.1.3, and 8.0.5 (!925 - merged) • Balasankar 'Balu' C • 17.3
   2. Bump Charts to 8.2.1, 8.1.3, and 8.0.5 (!924 - merged) • Balasankar 'Balu' C • 17.3
2. Tag 1.2.1 in canonical with a matching tag descrption - Version 1.2.1 - supports GitLab Charts 8.2.1, 8.1.3, 8.0.5
3. Confirm that publish jobs in the tag pipeline in Canonical repo has completed.
4. Confirm the tag was mirrored to dev
5. Confirm that the Release has been created with the correct content in the tag message and Release description..
6. OLM bundle testing has been completed
7. Release to OperatorHub.io.
8. Release to OpenShift OperatorHub.io
9. Submit OLM bundle for OpenShift certification

Using publish.sh script is recommended for the release-related steps:

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 OpenShift OperatorHub
• redhat-marketplace for OpenShift Certified Operators