Story (Required)

• As a part of this epic, the upstream argocd-operator introduces a field in the CR that enables the argo rollout ui in the dashboard. But that is using public quay image. We need to replace that with redhat registry images.
• As a gitops-operator user trying to enable rollout UI in my argocd instances, I want that my instances use official registry images in my product.

Background and Approach (Required)

• Argo Rollouts is tech preview in OpenShift GitOps and does not include any UI in the OpenShift Console. While longer term a dynamic plugin for the console is needed, a short term measure for providing a UI would be to enable the Rollouts extension in the Argo CD UI that GitOps already delivers.
• We need to make use of openshift hooks to replace the image set by the argocd-operator and to replace the extension_url env variable.
• The redhat registry image needs to be created from - https://github.com/argoproj-labs/argocd-extension-installer/tree/main
• and the extension_url can be either not needed or set to file-path to support future use cases.

Out of Scope

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

Dependencies

• Depends on the successful registry build of the extension installer image

Acceptance Criteria (Mandatory)

• The gitops-operator reconciles the argocd CR and if enableRolloutUI is present then replace/update to official registry images
• e2es and unit test to validate the same

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository/project.
• 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.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.