docs: clarify that workspace name derives the Kubernetes namespace - #1606
docs: clarify that workspace name derives the Kubernetes namespace#1606redhat-chai-bot wants to merge 37 commits into
Conversation
The docs described the workspace name field as just a "Display name". In reality, the platform derives the project name (Kubernetes namespace) from it. This is globally unique, immutable after creation, and subject to K8s naming rules. Add a new section documenting the derivation rules, uniqueness constraint, and immutability. Update the creation table and General settings section accordingly.
✅ Deploy Preview for cheerful-kitten-f556a0 canceled.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughDocumentation now explains how a Workspace Name produces a Kubernetes project name. It documents derivation rules, collision behavior, and immutability. Workspace settings now distinguish editable workspace fields from the read-only project name. ChangesWorkspace Naming Documentation
🚥 Pre-merge checks | ✅ 7 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (7 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/src/content/docs/concepts/workspaces.md`:
- Around line 53-54: The docs claim "Workspace name (display name) and
description — Update at any time" but this is only true on OpenShift; on vanilla
Kubernetes these fields are not editable. Update the text for the "Workspace
name (display name) and description" entry in
docs/src/content/docs/concepts/workspaces.md to clearly state the difference
(e.g., "OpenShift: editable at any time; vanilla Kubernetes: read-only after
creation") and/or link to the "Workspace name and project name" section for
platform-specific behavior so readers know the editability depends on the
underlying platform.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 068b9d0b-5070-48c8-ab8e-1269579107a8
📒 Files selected for processing (1)
docs/src/content/docs/concepts/workspaces.md
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
The docs described the workspace name field as just a "Display name". In reality, the platform derives the project name (Kubernetes namespace) from it. This name is globally unique on the cluster, immutable after creation, and subject to Kubernetes naming rules.
Changes
generateWorkspaceName)Slack thread: https://redhat-internal.enterprise.slack.com/archives/C09KMNSNUDT/p1779781417071479
Summary by CodeRabbit