Fix OLM Image Publication

[nathanjsweet]

Since March 2023 image publication has been broken. Images are published to the openshift repository for operators, but the images published can only be referenced by hash and not tag.

It seems that starting Feb 12 (with the <some_hash>-v1.12.6 tag) we started pushing a manifest list, always pointing to two things - the actual image and some other 1.2 kB file. That could be the root cause of the issue since Redhat doesn't support manifest lists.

The two options to fix this are:

a) Rebuild the container as a simple OCI image with no manifest list, push that to the incoming registry, run Preflight on it and then publish it.
OR
b) Switch to an external registry (including a partner-owned quay.io repo) and don't select Red Hat proxy-based 'hosting'. Then they can use manifest-based images.

[fgiloux]

Looking at the latest release

• the deployment
• the ClusterServiceVersion

reference images by digest.

Checking one of the image references: registry.connect.redhat.com/isovalent/cilium-olm@sha256:af9d1eda734b76ce8f2b5497ac4dc3be3b8449bf714166c9748f3d3695fde142
It is a single image for amd64 architecture not a manifest list.

looking at the operator image in Red Hat container catalog
it is also a single image.

Bundle images are architecture agnostic (no binaries).

I have successfully installed the operator on OpenShift, admittedly using the repo manifests and not the OLM bundle.

That said it is not optimal that manifest lists are not used. It prevents using the operator on non amd (arm) architectures.

I would propose to close this issue and to open a new one to enable multi-arch support. Let me know if I have missed something?