> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/how-to/forcefully-delete-kubernetes-pod.md).

# Forcefully Delete Kubernetes Pod

## Problem

* A pod is stuck in **terminating** state as per the Kubectl output.
* Deletion of pod fails even after running the command.

{% tabs %}
{% tab title="None" %}

```none
$ kubectl delete pod [pod_name] -n [namespace] --grace-period 0
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions

## Procedure

1. Verify that the container(s) associated with the pod isn't running on the node. This can be verified by identifying the container and the node name using the command below.

{% tabs %}
{% tab title="None" %}

```none
$ kubectl describe pod [pod_name] -n [namespace]
```

{% endtab %}
{% endtabs %}

2. SSH into the node and verify that that the container associated isn't running by running the following command.

* See [this article](https://platform9.com/docs/v5.6/kubernetes/containerd-commands-and-info#container-commands) for more details on containerd commands.

```none
$ docker ps
{% endtab %}
{% tab language="bash" title="containerd" %}
$ ctr -n k8s.io containers list
```

3. Once it's verified that the container isn't present, run the following command to delete the pod forcefully.

{% tabs %}
{% tab title="None" %}

```none
$ kubectl delete pod [pod_name] -n [namespace] --grace-period 0 --force
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/how-to/forcefully-delete-kubernetes-pod.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.