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

multi-user: Namespace Pipeline Definitions #4022

Closed
yanniszark opened this issue Jun 18, 2020 · 4 comments
Closed

multi-user: Namespace Pipeline Definitions #4022

yanniszark opened this issue Jun 18, 2020 · 4 comments
Assignees
Labels
cuj/multi-user help wanted The community is welcome to contribute. lifecycle/frozen status/triaged Whether the issue has been explicitly triaged

Comments

@yanniszark
Copy link
Contributor

yanniszark commented Jun 18, 2020

@Bobgy @IronPan I understand that the current state of Pipelines is that Runs/Experiments are namespaced, but pipeline definitions aren't.
I recall from an older discussion that:

  • You mentioned that users want a global pipeline registry, which is a very valid use-case, so that's why you keep pipeline definitions global for now.
  • We discussed about having both namespaced and global pipelines, based on an extra field in the database schema.

Given that pipeline definitions are essentially code and it doesn't seem reasonable to ask all teams to share all their code, what is your plan about supporting namespaced pipeline definitions (alongside global pipeline definitions), so that teams can keep their pipelines/code isolated?
I couldn't find a relevant issue so I created a new one.

@Bobgy
Copy link
Contributor

Bobgy commented Jun 19, 2020

/cc @IronPan

I don't think we have a plan to support that unless we gather further feedback. You are welcome to contribute the feature flag.

@Bobgy Bobgy added cuj/multi-user help wanted The community is welcome to contribute. status/triaged Whether the issue has been explicitly triaged labels Jun 19, 2020
@stale
Copy link

stale bot commented Sep 18, 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 lifecycle/stale The issue / pull request is stale, any activities remove this label. label Sep 18, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Sep 23, 2020

/lifecycle frozen

This is one of the top feature requests from multi user support issue.

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen and removed lifecycle/stale The issue / pull request is stale, any activities remove this label. labels Sep 23, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Nov 4, 2020

Duplicate of #4197

Let's use that issue to track this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuj/multi-user help wanted The community is welcome to contribute. lifecycle/frozen status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Development

No branches or pull requests

4 participants