Epic Goal

• Application CR(s) generated from an ApplicationSet seems to have a restriction that it would be created in the same namespace. This behavior should be changed. With OpenShift GitOps v1.7 we support Argo CD to read Applications in any namespace.
  
  Users should be able to achieve this using ApplicationSet controller as well.

Why is this important?

        - Many OpenShift GitOps customers use Application Set controller to create applications to deploy applications or infrastructure. Currently the applicationSet controller created using the OpenShift-GitOps instance can only deploy the applications in the same namespace.
         This was fine till OpenShift-GitOps v1.6.z but with the latest versions we support applications in any namespace. which means an Argo CD Instance can read applications not just from the namespace where it is deployed in, but also from other namespaces.
         We should allow users to create these applications in multiple namespaces using ApplicationSet controller as well.

Acceptance Criteria (Mandatory)

• Applications can be created using ApplicationSet controller.
• Add unit tests
• Add End to End tests
• Publish a blog and add documentation with examples

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment