Last active
May 22, 2024 19:07
-
-
Save superbrothers/b428cd021e002f355ffd6dd421b75f70 to your computer and use it in GitHub Desktop.
Kubernetes: Delete all objects in the namespace
This file contains 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
kubectl delete "$(kubectl api-resources --namespaced=true --verbs=delete -o name | tr "\n" "," | sed -e 's/,$//')" --all |
This file contains 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
#!/usr/bin/env bash | |
# | |
# kubectl-delete_all is a utility to delete all objects in the namespace. | |
[[ -n "$DEBUG" ]] && set -x | |
set -eou pipefail | |
exec kubectl delete "$(kubectl api-resources --namespaced=true --verbs=delete -o name | tr "\n" "," | sed -e 's/,$//')" --all "$@" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@scheung38's question, I think, is "Why bother with this plugin? Why not just delete the namespace itself, thereby implicitly deleting all of the objects within it?"
Depending on your roles and rolebindings, you might not have access to delete non-Namespaced objects (which a Namespace is), or re-create them. Sometimes Namespace deletions also get "stuck" on finalizers. So, deleting the contents of the Namespace without deleting the Namespace itself certainly is useful in some contexts.