You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to get your feedback on the current Argo workflow configurations we have been using for the local setup.
As you know, Argo workflow is using namespace scoped configurations (https://argoproj.github.io/argo-workflows/managed-namespace/) i.e. allowing us to have the argo services as well as the workflows only on the same namespace (argo) but the production cluster is configured with a cluster-scope i.e. allowing us to use other namespaces for workflows as well.
This is not a major limitation as such for local development but It kinda restricts us from using other namespaces for workflows and it will be nice to have a setup which is similar to production cluster for local playground as well.
Looking forward to hearing your thoughts on this.
Contributors: Infant Alex & Stig
The text was updated successfully, but these errors were encountered:
Hi,
We would like to get your feedback on the current Argo workflow configurations we have been using for the local setup.
As you know, Argo workflow is using namespace scoped configurations (https://argoproj.github.io/argo-workflows/managed-namespace/) i.e. allowing us to have the argo services as well as the workflows only on the same namespace (
argo
) but the production cluster is configured with a cluster-scope i.e. allowing us to use other namespaces for workflows as well.This is not a major limitation as such for local development but It kinda restricts us from using other namespaces for workflows and it will be nice to have a setup which is similar to production cluster for local playground as well.
Looking forward to hearing your thoughts on this.
Contributors: Infant Alex & Stig
The text was updated successfully, but these errors were encountered: