Story (Required)

At present, Argo CD agent requires that the principal namespace must not contain any Argo CD Applications. That is:

• Argo CD Applications should be in an 'applications in any namespace' namespace
• The only 'applications in any namespace' namespace should be argo cd agent namespaces.

That is, we do not currently support the case where a user wants to use Argo CD to do 2 things:
A) Deploy to 1 or more non-argo-cd-agent clusters
B) Deploy to 1 or more argo-cd-agent-managed cluster.

At this point, you must choose to either A), or B), but not both at the same time.

This story/epic are about allowing users

See https://github.com/argoproj-labs/argocd-agent/issues/708 for details

Acceptance Criteria (Mandatory)

• See GitHub issue and details above
• Users are able to deploy Argo CD applications to both agent and non-agent clusters via principal Argo CD
  • Redis proxy/resource proxy features work for both agent/non-agent Applications
• Upstream docs are updated
• Look at downstream docs and see if they need to be updated

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.