Story (Required)

• As an OpenShift GitOps Admin user, I want to configure Argo CD Image Updater using the Argo CD CR, so that I can use the Argo CD Image Updater to manage application images in OpenShift cluster.

Background and Approach (Required)

The following will be split into multiple stories:

• Create a new section in Argo CD CR spec to enable/disable argocd image updater.
• If Argo CD Image Updater is enabled in the Argo CD CR, then the operator has to create a deployment object for Image Updater. (5pts)
• Any additional routes, secrets, etc that is required for the functioning of the Image Updater needs to be enabled as well. (5pts)
• if the Image Updater is disabled in the spec, then the associated deployments, secrets, configmaps, routes should be removed as well. (5pts)
• The CSV manifest in the operator bundle must point to the productized version of the Image Updater (container image) (5pts)

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.