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

Multiteam collaboration support #2042

Closed
maryoush opened this issue Jan 23, 2020 · 4 comments
Closed

Multiteam collaboration support #2042

maryoush opened this issue Jan 23, 2020 · 4 comments

Comments

@maryoush
Copy link
Contributor

maryoush commented Jan 23, 2020

Summary

Was wondering about potential capabilities or mitigations of ArgoWorkflow in order to support that multi-team can work on single workflow. The most aspects are security where minimal visibility of steps between teams/namespaces need to be kept.

  • Each team can provide own step in separate namespace
  • Each team can test its step separately (in own namespace)
  • Each step can use dedicated credentials (e.g for backing service being called)
    no other team can use that /see that credentials.
  • Workflow owner (namespace), account has limited access to get each'es steps dedicated credentials/configuration.

Reading some lines of your document that shows that step per name space deployment is not supported

Also multi service accounts is not possible for each step.

All pods in a workflow run with the service account specified in workflow.spec.serviceAccountName,
or if omitted, the default service account of the workflow's namespace 

Is this anything on your backlog addressing that scenario ?

@maryoush
Copy link
Contributor Author

Are there any plans to support cross namespace deployment for workflow steps ?

@simster7
Copy link
Member

We are having abstract talks on the allowing this behavior, but haven't prioritized it yet. Regardless, I definitely wouldn't expect this to be available before 2.6.

@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 1, 2020
@stale stale bot closed this as completed Jul 9, 2020
@alexec
Copy link
Contributor

alexec commented Jan 14, 2021

See #3523

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

3 participants