Orkestra should use the ApplicationGroup namespace as the namespace for Argo workflows
Open
chore
size : S
- Dominant language
- Go
- Stars
- 112
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Currently, we use always use the `orkestra` namespace to run the argo workflows. Instead of using this always, we should use the `ApplicaitonGroup` namespace and generate the workflows in that namespace. This will allow teams that have security models that separate their logic into different namespaces to use multiple application groups in different namespaces.
Contributor guide
Assessment
This issue has not been assessed yet.