-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
4.15.0
-
No
-
False
-
Description of problem:
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 Quay container security operator which no longer works on OCP 4.15.
Version-Release number of selected component (if applicable):
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
How reproducible:
Everytime
Steps to Reproduce:
Deploy any imageCheck the pod.status.containerStatuses.imageID and see it contains an alphanumeric string and not the resolved digest
Actual results:
An alphanumeric string.
Expected results:
The resolved digest of the image
Additional info:
- is duplicated by
-
OCPBUGS-27321 image id is not correct when creating pods using manifests list imagestream
- Closed
- is related to
-
RFE-4608 Expose digest of the image executed in a Pod
- Accepted