chore: add script to force delete a namespace#1345
Merged
lemaitre-aneo merged 1 commit intomainfrom Dec 27, 2024
Merged
Conversation
167be79 to
a0cf8e0
Compare
jordancarrier
previously approved these changes
Dec 27, 2024
a0cf8e0 to
e1cf789
Compare
|
jordancarrier
approved these changes
Dec 27, 2024
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
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.



Motivation
Sometimes, when destruction goes wrong, the kubernetes namespace might end up being undeletable by conventional means. In those cases, even
kubectl delete namespace NAME --force --grace-period=0does nothing.Description
Add a script to remove all the finalizers of the namespace to tell kubernetes that the namespace has now been finalized.
Impact
This script should be used only as a last resort as it might leave resources alive.
Checklist