➹ New Feature implementation request

While debugging why the CI would not run on #1127, I found that the integration tests do not log pod events on failures, only pod logs and the general error code (CreateContainerConfigError, see this run for an example). Having the pod events would have immediately shown what the problem was (the container was trying to run with the root user, but had runAsNonRoot set to true).

Can we somehow surface this information in the CI logs to aid in debugging? At the moment, the logging logic seems to operate on the level of jobs, not pods, so I am not sure how exactly we would get to that information (it is not shown on the job events, only the pod events).