Overriding agent image values also overrides the FIPS proxy image values

[ryan-at-ld]

If I have spec.global.fips.enabled: true in my DatadogAgent resource and I also override the agent image name or tag (add spec.override. nodeAgent.image.tag: "7.58.1", for example), the overridden value is also applied to the FIPS proxy image. As a result, the FIPS proxy image is no longer valid and the pods can't start due to image pull errors. If I'm understanding the operator code correctly, the bug is in this for loop. It assumes that every container uses the same image. Modifying the loop to skip the fips-proxy container should fix the issue.

[khewonc]

@ryan-at-ld Thanks for reaching out. I'll add a card in our backlog to fix this. I think it's possible a user may want to override the fips-proxy image settings so my first thought is that if we add something to be able to override the image settings at the container level, that should work