Story (Required)

Please note that the same issue is happening when spec.version is overwritten in RolloutManager as well.
In this case it's even worse as argo-rollout pods fail to start complaining that file '/plugins/rollouts-trafficrouter-openshift/openshift-route-plugin' cannot be found.
This plugin is set in argo-rollouts-config ConfigMap and it looks like only argo-rollout images from registry.redhat.io/openshift-gitops-1 contain it.
When GitOps operator sets upstream images to be used - argo-rollout pods crash.

Please fix this issue in GitOps operator logic processing RolloutManager CR's.

Background and Approach (Required)

• <Describes the context or background related to this story. Include deeper motivation of user/persona if relevant (5 whys)>
• <Description of the general technical path on how to achieve the goal of the story. Include details like JSON schema, class definitions.>

Out of Scope

• <Defines what is not included in this story.>

Dependencies

• <Describes what this story depends on. Dependent stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• <Describe edge cases to consider when implementing the story and defining tests.>
• <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story.>

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.