When building the Compliance Operator, we tag each container with a version:

https://github.com/ComplianceAsCode/compliance-operator/blob/master/images/must-gather/Containerfile#L17

https://github.com/ComplianceAsCode/compliance-operator/blob/master/images/openscap/Containerfile#L18

https://github.com/ComplianceAsCode/compliance-operator/blob/master/images/operator/Dockerfile#L30

https://github.com/ComplianceAsCode/compliance-operator/blob/master/bundle.openshift.Dockerfile#L21

The problem is that don't have a tool to make sure all these versions stay consistent during a release, which becomes apparent when looking at the tags through the Red Hat catalog:

https://catalog.redhat.com/en/software/containers/compliance/openshift-compliance-rhel8-operator/607dc35087c834779d776118#

Konflux uses the version label associated with the image as a tag in the registry. All the container images should be the same.

In our case, the bundle image as the right tag, but the other images do not. We should have something to make sure these versions stay consistent and do not drift from one another, which can lead to confusion if you're looking at container images from the same bundle and they have different semantic version tags.

Based on our testing, we're still able to install the operator using the latest version, and the version reported through OLM is correct, meaning this is likely only a cosmetic issue, but something we should fix to reduce confusion.