Background and Approach (Required)

• Argo cd agent uses a redis proxy to allow Argo CD on principal to view child resources of agents.
• This requires proxy communication between argo cd (principal), redis (principal), and redis (agent).
• This story is about adding E2E tests to verify that when argocd agent is installed via operator, that redis proxy functionality works as expected

Acceptance Criteria (Mandatory)

• E2E tests to verify redis proxy functionality works in managed and autonomous modes, using the existing configuration we are already using in E2E tests.

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.