Publish registry operator to OpenShift OperatorHub

[michael-valdron]

Which area/kind this issue is related to?

/kind task

/area registry
/area releng

Issue Description

As with OperatorHub.io (#1211), we would like to make the devfile registry operator available under the OpenShift OperatorHub community catalog. Since the operator is published under OperatorHub.io already, we can use the same bundle for this publication.

Related discussion: #410 (comment)

Acceptance Criteria

• Ensure bundle files are up to date and placed under the following directory structure within a folk of redhat-openshift-ecosystem/community-operators-prod: https://docs.openshift.com/container-platform/4.13/operators/understanding/olm-packaging-format.html
• Create a PR of these change to the folk within the redhat-openshift-ecosystem/community-operators-prod repository and merge once approved
• Manually check that the operator shows up on the OpenShift catalog before closing this issue or making any announcements

[michael-valdron]

Opened PR redhat-openshift-ecosystem/community-operators-prod#3615 to publish a bundle release of the registry operator to OpenShift OperatorHub catalog.

Currently there are a few job failures differing from k8s-operatorhub/community-operators#3287 OperatorHub.io publication. To fix these, I need to perform the following:

• Provide a fix to remove the v prefix from the container image version tag
• Investigate and provide a fix for setting specific OpenShift version support as the registry operator only supports 4.12 and 4.13
• Investigate why 4.12 and 4.13 deploy jobs are failing and provide any needed fixes
• Cut a new release for any changes done, current release (0.1.3) will only be available on OperatorHub.io

Update: all failing jobs were fixed by suggestion from redhat-openshift-ecosystem/community-operators-prod#3615 (comment))

[michael-valdron]

Opened PR redhat-openshift-ecosystem/community-operators-prod#3615 to publish a bundle release of the registry operator to OpenShift OperatorHub catalog.

Currently there are a few job failures differing from k8s-operatorhub/community-operators#3287 OperatorHub.io publication. To fix these, I need to perform the following:

• Provide a fix to remove the v prefix from the container image version tag Update: issue fixed by suggestion from operator [N] registry-operator (0.1.3) redhat-openshift-ecosystem/community-operators-prod#3615 (comment))

• Investigate and provide a fix for setting specific OpenShift version support as the registry operator only supports 4.12 and 4.13

• Investigate why 4.12 and 4.13 deploy jobs are failing and provide any needed fixes

• Cut a new release for any changes done, current release (0.1.3) will only be available on OperatorHub.io

Update: None of these are necessary, adding com.redhat.openshift.versions: <versions> as suggested in redhat-openshift-ecosystem/community-operators-prod#3615 (comment) fixed the all the failing jobs.

[michael-valdron]

Additional release process step to add com.redhat.openshift.versions to annotations.yaml documented: #1194 (comment)

[michael-valdron]

redhat-openshift-ecosystem/community-operators-prod#3615 has been merged and bundle is now available under the community catalog.

A few UI issues remain for the entry:

1. Icon which is visable on OperatorHub.io is not visible on the OpenShift catalog
2. Code blocks are formatting on one line instead of being multi-line

OperatorHub.io

OpenShift 4.13 OperatorHub catalog

We need to investigate and fix these before closing out this issue.

[michael-valdron]

Opened an issue to track the fix for #1301 (comment): #1354

#1354 will need to be resolved before the demo for these changes can be done.

[michael-valdron]

#1354 has been resolved and this issue is unblocked: #1354 (comment)

Producing video demo to complete this issue.

[michael-valdron]

Producing video demo to complete this issue.

Video demo is completed and this item is now complete.