Talking to Derrick (containers team), it looks like the issue is that 1.6.8-2 is not actually released so the image doesn't exist in our registry despite the operator referencing it. There is an issue with the registry where it's returning the 'unsupported: V2 schema 1 manifest digests are no longer supported' instead of a correct 404.
 
This looks like a bug with the operator as we shipped 1.6.8-3.
 
We should be pulling registry.redhat.io/integration/camel-k-rhel8-operator@sha256:a54df008a216b145d39abc0bf52ae165bd482fdccfd77a4efc530a2b4b33f87d
 
Which is the release 3 image.
 
If you look at the internal registry, you can see the image used by the operator is the release 2:
skopeo inspect docker://registry-proxy.engineering.redhat.com/rh-osbs/integration-camel-k-rhel8-operator@sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf1937797f7ae908 | egrep 'Name|\"version\"|release'"Name": "registry-proxy.engineering.redhat.com/rh-osbs/integration-camel-k-rhel8-operator",
"release": "2",
"version": "1.6.8"

 
skopeo inspect docker://registry.redhat.io/integration/camel-k-rhel8-operator@sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf193779deadbeefFATA[0000] Error parsing image name "docker://registry.redhat.io/integration/camel-k-rhel8-operator@sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf193779deadbeef": reading manifest sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf193779deadbeef in registry.redhat.io/integration/camel-k-rhel8-operator: unsupported: V2 schema 1 manifest digests are no longer supported for image pulls. Use the equivalent V2 schema 2 manifest digest instead. For more information see https://access.redhat.com/articles/6138332

 
instead of returning a 404 it's returning this error message -> https://issues.redhat.com/browse/REGISTRY-327 seems EXD/SP already noticed this issue (but didn't bother to tell me)