Story (Required)

• As an OpenShift GitOps Admin user trying to use the Argo CD agent, I want to install the agent component via an helm chart on the remote cluster and configure it to connect with the Principal component of an Argo CD instance manged via the OpenShift GitOps Operator.

Background and Approach (Required)

• Helm chart based installation of the agent component is preferred.
• Helm chart should be built on a nightly basis and published to a helm registry, preferably (ghcr.io) where Argo CD Helm chart is published as well.
• The helm chart should be publicly available and must not require any credentials to install it.
• It should be possible to override the container images used in the agent component deployment via the values.yaml file so that productized version of the container images can be used by OpenShift GitOps customers.

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.