Why do we run imageDigestExporter after each step in a taskrun?

[dibyom]

The imageDigestExporter container writes the digest of any built images to the container's terminationMessagePath which is then parsed by the taskrun controller in order to update the taskrun's status with the image digests.

The container only gets added if a task contains an output resource of type image. However, it gets added after each step as opposed to being added just once (after all the regular steps). The container itself takes as input all the output images that will be produced in a task, and writes the digest for all of them. So, it is unclear to me why we need to run it after each step.

Does anyone know why we need to run the container after each step? Maybe @nader-ziada or @imjasonh ?

/kind question

[vdemeester]

Looking into that, I think this is working like that to support multiple image built in different steps. but looking at the code, only one step/container is needed.

/assign
/kind bug
/remove-kind question

[tekton-robot]

@vdemeester: Those labels are not set on the issue: kind/bug

In response to this:

Looking into that, I think this is working like that to support multiple image built in different steps. but looking at the code, only one step/container is needed.

/assign
/kind bug
/remove-kind bug

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.

[tekton-robot]

@vdemeester: Those labels are not set on the issue: kind/question

In response to this:

Looking into that, I think this is working like that to support multiple image built in different steps. but looking at the code, only one step/container is needed.

/assign
/kind bug
/remove-kind question

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.