Release RSCT Operator

[varad-ahirwadkar]

Upstream - https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators

Reference - https://redhat-openshift-ecosystem.github.io/operator-pipelines/#add-your-operator
https://k8s-operatorhub.github.io/community-operators/pull_request_template/

• Fork project - redhat-openshift-ecosystem/community-operators-prod
• Place the operator in the target directory
  • Add Operator Bundle to the forked repo
  • Preflight tests to verify that partner-submitted containers meet minimum requirements for Red Hat Software Certification
  • Operator certification - https://connect.redhat.com/
• Configure ci.yaml file - operator-ci-yaml
  • Setup reviewers
  • Operator versioning strategy
• Sign Your Work - contributing-prerequisites
• Make a pull request

Requirements for Software Product Certification
Reference - Red Hat OpenShift Software Certification Policy Guide

• The Operator must update the status field of each Custom Resource
• The Cluster Service Version (CSV) in the Operator bundle must include all the fields indicated as required in the CSV fields
  • spec.customresourcedefinitions.specDescriptors
  • categories: Comma-separated string of the community-operators/categories list that applies to this product
  • CSV in Operator bundle must indicate all the container images needed to perform its function, using the spec.relatedImages field.

[varad-ahirwadkar]

Above steps are mandatory to release operator in RedHat's community operator.

To release the RSCT Operator on OperatorHub.io, a subset of the above steps are required.

Operator has been released - https://operatorhub.io/operator/rsct-operator.

Repository: https://github.com/k8s-operatorhub

PR: k8s-operatorhub/community-operators#5241