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

Skip specify namespace for CreateRun APIs #3290

Closed
IronPan opened this issue Mar 17, 2020 · 5 comments · Fixed by #3477
Closed

Skip specify namespace for CreateRun APIs #3290

IronPan opened this issue Mar 17, 2020 · 5 comments · Fixed by #3477
Assignees
Labels
area/backend cuj/multi-user status/triaged Whether the issue has been explicitly triaged

Comments

@IronPan
Copy link
Member

IronPan commented Mar 17, 2020

In previous release, when creating runs in multi-user mode, user need to specify a namespace.
This is no longer needed in the future, since the user will always specify an experiment, and an experiment always belongs to a single namespace.

This issue tracks the work to revert the change done previously.

@chensun
Copy link
Member

chensun commented Apr 6, 2020

/close

@k8s-ci-robot
Copy link
Contributor

@chensun: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Bobgy
Copy link
Contributor

Bobgy commented Apr 8, 2020

A follow up bug fix: #3477

@Bobgy
Copy link
Contributor

Bobgy commented Apr 8, 2020

/reopen

@k8s-ci-robot
Copy link
Contributor

@Bobgy: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend cuj/multi-user status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants