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

Need a user interface and/or documentation for the Viewer CRD #1026

Closed
vicaire opened this issue Mar 23, 2019 · 5 comments
Closed

Need a user interface and/or documentation for the Viewer CRD #1026

vicaire opened this issue Mar 23, 2019 · 5 comments

Comments

@vicaire
Copy link
Contributor

vicaire commented Mar 23, 2019

We need a user interface and/or documentation for the Viewer CRD:

  • So that users can keep track of their instances of Tensorboard or other viewers.
  • So that users do not forget to delete them once they do not need them.

Ideally, the viewer CRD should automatically terminate processes if they have not been used for a while (though this is harder to do).

@rileyjbauer
Copy link
Contributor

Is there design work here?
@ajayalfred

@vicaire
Copy link
Contributor Author

vicaire commented Mar 26, 2019

Yes, there should be design work needed.

@ajayalfred
Copy link
Contributor

I'll setup a meeting to discuss scope of the design work.

@rileyjbauer
Copy link
Contributor

@jingzhang36 do you think you can take this on?

@neuromage
Copy link
Contributor

I think we can close this as a duplicate of kubeflow/kubeflow#3578 which @kimwnasptd has volunteered to tackle.

magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
add two test cases to verify
- taskruns/runs execution sequence
- caching function

Signed-off-by: Yihong Wang <yh.wang@ibm.com>

Signed-off-by: Yihong Wang <yh.wang@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants