Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-7010

Argo Agent : Provide option in Argo CD CR to enable/disable Principal Component

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.17.0
    • None
    • None
    • None
    • GitOps Scarlet Sprint 16, GitOps Scarlet Sprint 17, GitOps Scarlet Sprint 18

      Story (Required)

      • As a OpenShift GitOps Admin user, I want to configure Argo CD Prinicipal Component using the Argo CD CR, so that I can use the Argo CD agent to connect remote clusters to the Argo CD Agent managed by OpenShift GitOps.

      Background and Approach (Required)

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

      Out of Scope

      *NA

      Dependencies

      • Productized version of the Argo CD Agent Principal component is made available in a container registry.

      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.

              jparsai Jayendra Parsai
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: