Pod status imageID field no longer contains the resolved image

[bcaton85]

In OCP 4.14 and previous, the pod.status.containerStatuses.imageID field contained the resolved image and digest that was used for the pod. In OCP 4.15 the imageID field seems to contain a generated alphanumeric string. Extracting the digest used by the pod is required for products like the container security operator which no longer works on OCP 4.15.

Version

Client Version: 4.13.0-202307100954.p0.ge4c9a6a.assembly.stream-e4c9a6a
Kustomize Version: v4.5.7
Server Version: 4.15.0-0.nightly-2024-01-18-050837
Kubernetes Version: v1.28.5+c84a6b8

Steps To Reproduce

1. Deploy any image
2. Check the pod.status.containerStatuses.imageID and see it contains an alphanumeric string and not the resolved digest

Current Result

An alphanumeric string.

Expected Result

The resolved digest of the image.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale