HOSTEDCP-1146: cpo: use CPO spec container image if it is a sha256 reference

[sjenning]

In preparation for an e2e to verify proper ControlPlaneRelease function, I noticed that containers that use the self-referencing image lookup by the CPO were using an image ref different from that of the CPO itself.

This occurs when the ControlPlaneRelease image is set to a release image that shares an identical CPO image with the Release image. In that case, the imageID still contains the Release reference to the image, since the sha256 is the same; only the registry path is different.

In order to verify that all HCP containers are using the ControlPlaneRelease image, we need all containers to reflect the expected registry path.

[sjenning]

cc @csrwng

[csrwng]

/lgtm

[openshift-ci-robot]

@sjenning: This pull request references HOSTEDCP-1146 which is a valid jira issue.

In response to this:

In preparation for an e2e to verify proper ControlPlaneRelease function, I noticed that containers that use the self-referencing image lookup by the CPO were using an image ref different from that of the CPO itself.

This occurs when the ControlPlaneRelease image is set to a release image that shares an identical CPO image with the Release image. In that case, the imageID still contains the Release reference to the image, since the sha256 is the same; only the registry path is different.

In order to verify that all HCP containers are using the ControlPlaneRelease image, we need all containers to reflect the expected registry path.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sjenning

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sjenning]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d806b54 and 2 for PR HEAD 8490b98 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 6ba4c1f and 1 for PR HEAD 8490b98 in total

[sjenning]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@sjenning: new pull request created: #3296

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.