From 8f974b4df541b75fc882ed2c38d70cb715c2abc6 Mon Sep 17 00:00:00 2001 From: Samuel Birocchi Date: Wed, 1 Aug 2018 15:27:39 -0300 Subject: [PATCH] Adding patch command to forceful delete stateful pod (#9627) --- .../tasks/run-application/force-delete-stateful-set-pod.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md b/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md index 323cdd57e5..76fc714da2 100644 --- a/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md +++ b/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md @@ -67,6 +67,12 @@ If you're using any version of kubectl <= 1.4, you should omit the `--force` opt kubectl delete pods --grace-period=0 ``` +If even after these commands the pod is stuck on `Unknown` state, use the following command to remove the pod from the cluster: + +```shell +kubectl patch pod -p '{"metadata":{"finalizers":null}}' +``` + Always perform force deletion of StatefulSet Pods carefully and with complete knowledge of the risks involved. {{% /capture %}}