Operator certification doesn't require separate image certification projects. The images are checked by preflight during the certification process.
The RH Partner Portal is undergoing big changes at the moment.
Details
TLDR; the OpenShift certification process is not 100% correct. Images in the OLM bundles are not the same as images in the RH portal.
It used to be the Stackable images were only available in one registry (docker.stackable.tech). Due to customer request, they are now also available on Harbor and quay.io. But the existing CI pipelines and RH portal projects haven't changed.
A quick overview of the RH projects
There three entities involved in publishing certified operators:
the container project - referenced the product images. These point to docker.stackable.tech right now.
the operator bundle - references a certification pipeline PR
the product listing - bundles 1. and 2., adds some more marketing material and makes sure that our operators are available in the RH catalogs and on https://catalog.redhat.com/software/search
Back to the problem
The certification PRs (the actual OLM bundles) now reference quay.io and not docker.stackable.tech. As of this writing (April 2024) the certification pipeline doesn't seem to care and it's not clear if this intended or an omission on RHs part.
A quick attempt to add quay.io images to the existing container projects failed.
$ check-container --registry quay.io --product airflow --image-version 24.3.0 --submit --token xxx
...
2024/04/05 14:57:34 could not submit to pyxis: could not update project: status code: 400: body: {"detail": "You cannot change container.repository and container.registry fields to specified values as the combination would no longer be unique.", "status": 400, "title": "Bad Request", "type": "about:blank", "trace_id": "0xc901192d34bf3434b5610bbff6314105"}
....
This means that we need new RH projects for the containers. The implications on the product listings and the certification pipelines are not 100% clear.
Will there be duplicated operators in the RH catalogs or will there be conflicts?
Will users be able to upgrade an operator from one project to an operator from the new project ?
...
Description
Update Sep 30 2024
Putting this on hold because:
preflightduring the certification process.Details
TLDR; the OpenShift certification process is not 100% correct. Images in the OLM bundles are not the same as images in the RH portal.
It used to be the Stackable images were only available in one registry (
docker.stackable.tech). Due to customer request, they are now also available on Harbor andquay.io. But the existing CI pipelines and RH portal projects haven't changed.A quick overview of the RH projects
There three entities involved in publishing certified operators:
docker.stackable.techright now.Back to the problem
The certification PRs (the actual OLM bundles) now reference
quay.ioand notdocker.stackable.tech. As of this writing (April 2024) the certification pipeline doesn't seem to care and it's not clear if this intended or an omission on RHs part.A quick attempt to add
quay.ioimages to the existing container projects failed.This means that we need new RH projects for the containers. The implications on the product listings and the certification pipelines are not 100% clear.
Will there be duplicated operators in the RH catalogs or will there be conflicts? Will users be able to upgrade an operator from one project to an operator from the new project ? ...