Skip to content

Stop offering the default namespace for app launches - #5

Merged
jbouder merged 1 commit into
mainfrom
no-default-namespace
Aug 14, 2026
Merged

Stop offering the default namespace for app launches#5
jbouder merged 1 commit into
mainfrom
no-default-namespace

Conversation

@jbouder

@jbouder jbouder commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • nebari-operator v0.1.0-alpha.20 rejects NebariApps in the default namespace, so the API now filters default and kube-* out of the launchable-namespace list — applied to both the configured allowedNamespaces allowlist and the managed-label fallback, covering the UI namespace dropdown, MCP describe_cluster, and launch validation.
  • Dev clusters no longer label the default namespace nebari.dev/managed=true.
  • Bumped the pinned OPERATOR_REF to v0.1.0-alpha.20 so local dev matches the new operator behavior.

Test plan

  • pytest in api/ — 28 passed, including a new test asserting default/kube-system are never offered in /capabilities and that launching into default returns 403.

🤖 Generated with Claude Code

nebari-operator v0.1.0-alpha.20 rejects NebariApps in the default
namespace, so the API now filters "default" and kube-* out of the
launchable-namespace list (both the configured allowlist and the
managed-label fallback), dev clusters no longer label default as
managed, and the pinned operator release is bumped to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jbouder
jbouder merged commit 4f9045f into main Aug 14, 2026
6 checks passed
@jbouder
jbouder deleted the no-default-namespace branch August 14, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant