Skip to content

Conversation

@mathis-marcotte
Copy link

Small fix to improve consistency in the default workspace volume name when creating a new Notebook.

I noticed that on initial load of the crud-web-apps/jupyter form, the default workspace volume name was "{notebook-name}-workspace".
But if you deleted that workspace volume, and then re-added a workspace volume to the Notebook you are creating, then the workspace volume name was "{notebook-name}-volume".

This PR is to FIX the default name of the workspace volume to always follow the same standard of "{notebook-name}-workspace" to match with the default configs.

Original PR here: kubeflow/kubeflow#7705

mathis-marcotte and others added 2 commits September 5, 2025 09:23
…t configs

Signed-off-by: Mathis Marcotte <84033116+mathis-marcotte@users.noreply.github.com>
@github-project-automation github-project-automation bot moved this to Needs Triage in Kubeflow Notebooks Dec 11, 2025
@google-oss-prow google-oss-prow bot added the area/backend area - related to backend components label Dec 11, 2025
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign orfeas-k for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot added area/frontend area - related to frontend components area/v1 area - version - kubeflow notebooks v1 size/S labels Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/backend area - related to backend components area/frontend area - related to frontend components area/v1 area - version - kubeflow notebooks v1 size/S

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

1 participant