-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Namespace option for Application when using 'Applications in Any Namespace' feature
2. What is the nature and description of the request?
When creating an ArgoCD Application in the UI, there is no field to set the namespace. If you are using Applications in Any Namespace feature, applications can be deployed in namespaces other than openshift-gitops. The only way using the UI template to pass in the namespace is by naming the application <namespace>/<application>. If the namespace is not specified, the application will be created in the openshift-gitops namespace. The proposal is to provide a drop down selection for namespaces based on the sourceNamespaces outlined in the ArgoCD App Project.
3. Why does the customer need this? (List the business requirements here)
Applications are frequently created in the openshift-gtiops namespace by developers by mistake when the application name does not follow the 'Applications in Any Namespace' naming convention. This causes permissions issues since that is not a valid sourceNamespace in our multi-tenancy environment.
4. List any affected packages or components.
OpenShift GitOps