Describe workspace storage without a form choice - #126
Merged
Merged
Conversation
The app form no longer asks where workspace storage lives. A workspace always uses the cluster's default storage class and keeps its code services, SSH runner and preparation jobs on one node. The docs drop the Storage step, say that an existing cluster needs exactly one default storage class, and mention that the API and MCP can still choose another class or a storage service.
csandanov
marked this pull request as ready for review
September 27, 2026 04:35
The Workspace page now calls the steps that run after cloning setup, so the storage notes say setup jobs too.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The development workspace docs describe a Storage choice in the app form. The form is dropping that choice: a workspace always uses the cluster's default storage class and runs on one node. This update removes the Storage step and says that an existing cluster needs exactly one default storage class. It also notes that the API and MCP can still choose another class or a storage service.
Merge when the app form without the Storage choice is live.
Changes
apps/workspaces.md):apps/index.md): the Development workspace section shows the generated working branch, with no storage choice.Validation
mkdocs build --strictpasses with local plugins. The Markdown-export hook was skipped because itsbs4dependency isn't installed locally, so CI will run it.