dd4ef1f939
Given we have migrated all our images from docker.io to ghcr.io - our `notebooks-v2` branch should reference the "proper" container registry. This commit updates the code to use: - `ghcr.io/kubeflow/kubeflow/notebook-servers` Affected areas: - `jupyterlab_scipy_180` and `jupyterlab_scipy_190` `imageConfig` entries - various test files Signed-off-by: Andy Stoneberg <astonebe@redhat.com> |
||
|---|---|---|
| .github/workflows | ||
| workspaces | ||
| .gitattributes | ||
| .gitignore | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
README.md
Kubeflow Notebooks
Kubeflow Notebooks lets you run web-based development environments on your Kubernetes cluster by running them inside Pods.
What is Kubeflow Notebooks?
Key features of Kubeflow Notebooks:
- Native support for JupyterLab, RStudio, and Visual Studio Code (code-server).
- Users can create notebook containers directly in the cluster, rather than locally on their workstations.
- Admins can provide standard notebook images for their organization with required packages pre-installed.
- Access control is managed by Kubeflow’s RBAC, enabling easier notebook sharing across the organization.
Installation
Currently, Kubeflow Notebooks must be deployed as part of a full Kubeflow platform (not as a standalone component).
Please refer to the Installing Kubeflow page for more information.
Documentation
The official documentation for Kubeflow Notebooks can be found here.
Community
Kubeflow Notebooks is part of the Kubeflow project, refer to the Kubeflow Community page for more information.
Connect with other users and the Notebooks Working Group in the following places:
- Kubeflow Slack - Join the
#kubeflow-notebookschannel. - Kubeflow Mailing List
Contributing
⚠️ Note ⚠️
We are currently moving the Kubeflow Notebooks codebase from
kubeflow/kubeflowto this repository (kubeflow/notebooks). For now, please continue to make contributions by raising PRs onkubeflow/kubeflow.
Please see the Contributing to Kubeflow page for more information.