Include violating image in logs produced by pod_trusted_repository policy about k-rail HOT 2 CLOSED

Hey @funkypenguin

Thanks for raising this issue, I can definitely understand the need for knowing which image was triggering the policy enforcement from the logs.

Here's a draft PR with one way we could attempt this, by adding it to the violation text.
#79 -- reading that again now I don't think the addIfUnique function is necessary, but it was a quick hack :)

Another option could be to change the ResourceViolation struct but I suspect that will involve broader changes.

from k-rail.

I merged @frenchi's change, released in v2.2.0.

Eventually I'd like to add support for custom fields though, and then we can include the image name and registry in distinct fields that can be queried on easily.

from k-rail.