The Jaeger operator, whether upstream or product, knows which images it should be using - including the version that it is managing.

Therefore the jaeger-production-elasticsearch.yaml and jaeger-all-in-one.yaml helm templates within Maistra's operator should not need to include the image explicitly.

The only issue is that when wanting to test against a particular version, the appropriate operator (from marketplace with configured operator source: rh-osbs-operators or redhat-operators-stage, would need to be used.

NOTE: Currently the agent node within the Jaeger CR's is not specifying the image - so it would be using the upstream jaeger-agent image.