> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.11/basic-cluster-operations/delete-cluster.md).

# Delete Cluster

You can delete a cluster when it is no longer required.

When you delete a cluster, following things will happen under the hood:

* Any pods or other ephemeral Kubernetes objects associated with the cluster are deleted.
* If any Virtual Machine instances were created by a Platform9 Cloud Provider as worker or master nodes during creation of this cluster, those instances will be deleted.
* Any persistent volumes that were mounted on either the cluster master or worker nodes or by cluster workloads will not be deleted. Those will remain intact.

{% hint style="info" %}
**Note**

You must be a Platform9 administrator to delete a cluster.
{% endhint %}

Follow the steps given below to delete a cluster.

1. Navigate to Infrastructure>Cluster.
2. Select a cluster.
3. Click Delete Cluster seen above the list of clusters.
4. You will be prompted to confirm your action.

The cluster is now deleted.


---

# 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 by asking a question.

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

```
GET https://docs.platform9.com/managed-kubernetes/5.11/basic-cluster-operations/delete-cluster.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 `automate deployments from our CI pipeline` 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.