Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Argo Workflows - scope #1

Open
vminfant opened this issue Aug 22, 2022 · 1 comment
Open

Argo Workflows - scope #1

vminfant opened this issue Aug 22, 2022 · 1 comment
Assignees

Comments

@vminfant
Copy link

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

@kjetilh33
Copy link
Contributor

Good suggestion. It makes sense to try and do cluster scope in order to make the dev workflow easier. Let me look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants