Improve New Release Process

[yuwenma]

This issue tracks the progress of improving the new release process.

Propose tag

• sub issue tracker Enhancement to propose_tag #3326
• Keep n-3 CRD versions in release bundle
• (TBD) Push tag to git

Push tag branch

• We have internal script to push the image. Need to improve the script and make it sharable.

Promote image to prod

• We have internal script to promote the image. Need to improve the script and make it sharable.

Legacy manifests

• Update ./crds based on config/crds/resources. File names are changed
• Update ./install-bundles based on the output from dev/tasks/build-release-bundle.
• Push git tag?

Manual Upgrade

• Publish the release-bundle.tar.gz for manual installation. feat:add manual release #3342 adds a script to build the release-bundle.tar.gz . We can either push it to GCS bucket (current approach) or GItHub assets or some other places that are more convenient for OSS users. Google doc needs to be updated accordingly.

Productize Image Promoter

• Make the release image promotor tool (staging-->prod) to be a stable tool in g3.

Automate the config for GKE Add-on

• Change the build process to use dedicated resources names rather than "*" for RBAC "ClusterRole" configconnector-operator-cnrm-viewer (required by GKE add-on presubmit)
• Fix the cnrm.cloud.google.com/version annotation versioning in "ClusterRole" configconnector-operator-cnrm-viewer

Documentation

• Update the playbook for new release process.