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

Argo CD Agent: Proxy redis traffic from principal to agent

XMLWordPrintable

    • GitOps Scarlet Sprint 14, GitOps Scarlet Sprint 15, GitOps Scarlet Sprint 16, GitOps Scarlet Sprint 17, GitOps Scarlet Sprint 18

      Story (Required)

      See parent epic/feature for details

      Background and Approach (Required)

      • See parent epic/feature for details

      Acceptance Criteria (Mandatory)

      • Principal's Argo CD instance connects to Argo CD Agent on redis proxy endpoint
      • Argo CD agent intelligently routes traffic to either the local principal Argo CD redis, or to agent Argo CD redis
      • For routing to agent Argo CD redis, redis messages are sent in a similar fashion to resource proxy

      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.

              jgwest Jonathan West
              jgwest Jonathan West
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: