Proposal Notebooks 2.0 // Workspace Spawner UI - Milestone 1

[ederign]

Notebooks 2.0 // Workspace Spawner UI - Milestone 1

This issue aims to discuss the scope of the first milestone for Kubeflow Workspace Spawner UI and gather more contributors.

Kubeflow Workspace Spawner is a UI from which end users create Workspace namespaced CRDs and where existing notebooks can be viewed/edited. This UI will be integrated and consumed in the Kubeflow Central Dashboard.

My proposal for the scope of this first milestone would be:

• As a user, I want to list workspaces from a given namespace;
• As a user, I want to CRUD a workspace;
• As a user, I want to connect to a workspace;
• As a user, I want to list workspace kinds;

As this is the first iteration, and I aim to iterate it quickly, I sugest postponing discussions around pagination, authorization, and other non-functional requirements. We can always do them in the subsequent iterations. Let's focus on having a working prototype to get momentum in the community.

Controller

• Notebooks 2.0 // Controller // Implement VirtualService reconciliation  #37
  • this issue is blocking the final "connect to workspace" user story, because without the VirtualService you can't connect to the Pod.

Backend

• Notebooks 2.0 // Backend // List Workspaces API #40
• Notebooks 2.0 // Backend // CRUD Workspaces API #49
• Notebooks 2.0 // Backend // Provide Workspaces Link #50
• Notebooks 2.0 // Backend // List WorkspaceKinds #51
• Notebooks 2.0 // Backend // List namespaces #53
• Notebooks 2.0 // Backend // CRUD Workspaces API #49
• Notebooks 2.0 // Backend // Update list workspaces JSON payloads #127
• Notebooks 2.0 // Backend // Update list workspacekinds JSON payloads #128
• Notebooks 2.0 // Backend // Reject invalid requests #129
• Notebooks 2.0 // Backend // add a rate limiting #131

Frontend

• Notebooks 2.0 // Frontend // Namespace selector #54
• Notebooks 2.0 // Frontend // Workspaces table #55
• Notebooks 2.0 // Frontend // Workspaces details #56
• Notebooks 2.0 // Frontend // CRUD workspace #57
• Notebooks 2.0 // Frontend // Workspaces table // Live mockup #136
• Notebooks 2.0 // Frontend // Workspaces table // Fetch workspaces list from backend #142
• Notebooks 2.0 // Frontend // Workspaces table // Filter workspaces #143
• Notebooks 2.0 // Frontend // Workspaces table // Delete workspace #144
• Notebooks 2.0 // Frontend // Workspaces table // Edit workspace #145
• Notebooks 2.0 // Frontend // Workspaces table // Start, restart and stop workspace #146
• Notebooks 2.0 // Frontend // Workspaces table // Workspace redirect status column #147
• Notebooks 2.0 // Frontend // Workspaces table // Workspace Kind column #148
• Notebooks 2.0 // Frontend // Workspaces table // Workspace Data Vol column #149
• Notebooks 2.0 // Frontend // Workspaces table // Workspace Connect column #150
• Notebooks 2.0 // Frontend // Workspaces table // Workspace CPU and RAM columns #151
• Notebooks 2.0 // Frontend // Workspaces details // Live mockup #156

chores

• Notebooks 2.0 // Backend // Deploy on Makefile #45
• Notebooks 2.0 // Backend // Auto generate Open API spec #46
• Notebooks 2.0 // Backend // Setup BDD and envtest on backend #47
• Notebooks 2.0 // Backend // Setup end to end tests #48
• Notebooks 2.0 // Frontend // Setup Basic Spawner App #52
• Notebooks 2.0 // Backend // add make lint check to GitHub actions #130
• Notebooks 2.0 // Backend // Enhance Local Development with Auto-Reload Functionality #135
• Notebooks 2.0 // Frontend // Setup kubeflow-ui-essentials repository #155

[mohamedch7]

Hello @thesuperzapper and @ederign,
I'm interested in contributing to Kubeflow, and I bring experience in both frontend and backend development. I’d love to assist wherever help is most needed. Please let me know if there are specific guidelines or initial tasks I should focus on. Excited to be part of this project!