-
Notifications
You must be signed in to change notification settings - Fork 790
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
Document the start/stop functionality of Notebooks and best practices #3101
Comments
hi @DanieleBaranzini, could you create this issue in the kubeflow/kubeflow repo instead were we track issues and questions around Notebooks? I want to use this issue to keep the discussion around the Notebook culling docs. But, if there's context from your issue we can document here then we can add a comment after we have debugged your issue. |
Hi @kimwnasptd , thanks I solved the issue about authentication today. So I would close this directly and feel free to drop out my thread in case. |
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. |
/close |
@varodrig: Closing this issue. In response to this:
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. |
based on comments from @kimwnasptd this is issue is now closed. |
Since start/stopping a notebook could lead to data loss, in case the data in the Pod is not backed by a PVC or are not part of the image. We've also seen users bumping into this kubeflow/kubeflow#6244.
Adding a section for starting/stopping notebooks as well as concerns around user data could be helpful to avoid data loss.
cc @kubeflow/wg-notebooks-leads @shannonbradshaw
The text was updated successfully, but these errors were encountered: