feat: allow deleting a namespace - #8
Merged
Merged
Conversation
Closes #4. Namespaces are now deletable end to end: - kube-core `delete_resource` handles the `namespaces` kind as a cluster-scoped delete (nodes stay excluded). - The frontend adds `namespaces` to DELETABLE_KINDS so the row/detail delete action appears. - Because deleting a namespace cascades to everything inside it, ConfirmDialog gains an optional type-to-confirm gate; namespace deletion requires typing the namespace name and shows a stronger warning before the button enables. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Merged
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.
Closes #4.
What
Namespaces can now be deleted from KubeFront (previously deliberately blocked).
kube-core::LocalKube::delete_resourcehandles thenamespaceskind as a cluster-scoped delete. Nodes remain non-deletable.namespacestoDELETABLE_KINDS, so the 🗑 action shows up in the namespaces list and detail panel. Works in both Direct and Remote modes (sharedkube-corepath).Safety
Deleting a namespace cascades to every resource inside it, so it gets an extra guard:
ConfirmDialognow supports an optional type-to-confirm field. For namespaces the dialog shows a stronger warning and the Delete button stays disabled until you type the namespace name exactly.Test
npm run build✓cargo fmt --all -- --check✓cargo clippy --workspace --all-targets -- -D warnings✓cargo test -p kubefront-core✓ (6 passed)🤖 Generated with Claude Code