[BUG] relatedImages are incomplete in the published bundle.

[libesz]

Is this the right place to submit this?

• This is not a question about how to use the sail-operator

Bug Description

After closing #216 and #243, it is expected to have a complete set of relatedImages in the published operator catalog bundle, which may be ever installed by the operator. In the 14th Aug nightly build, the only new image (compared to earlier bundles) is ztunnel, while pilot, proxyv2 and cni appears to be missing. The incomplete relatedImages section breaks any image mirroring effort based on opm or other catalog index based tooling.
The complete relatedImages section of the current nightly build is:

    "relatedImages": [
        {
            "name": "v1_22_3.ztunnel",
            "image": "docker.io/istio/ztunnel:1.22.3"
        },
        {
            "name": "",
            "image": "gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0"
        },
        {
            "name": "",
            "image": "quay.io/community-operator-pipeline-prod/sailoperator@sha256:4b84e4c19956e198e9d10c3f2314ebdfca3cccd0e3efe36291ea7d98cdfd6017"
        },
        {
            "name": "",
            "image": "quay.io/maistra-dev/sail-operator:0.1-nightly-2024-08-14"
        }
    ]

Operator Version

sailoperator.v0.1.0-nightly-2024-08-14

Link to Gist with Logs

No response

Additional Information

No response

[dgn]

it's really strange- I can't reproduce this on my machine. whenever I run the target, all the relatedImages are filled in correctly

[dgn]

we most likely found the issue... outdated version of yq in build container which has a bug we're affected by. updating the build container now

[dgn]

the latest nightly builds and the 0.1.0-rc1 CSV have the correct relatedImages, closing this