> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/containers/managed-kubernetes/how-tos/delete-node-pool.md).
# Delete a Node Pool
Delete a node pool from a Managed Kubernetes cluster on IONOS CLOUD using the DCD.
You can delete node pools from the [DCD](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#data-center-designer-dcd).
{% hint style="info" %}
**Note:** Avoid accessing the target data center while Managed Kubernetes is provisioning nodes, as concurrent manual interaction can cause undesirable results.
{% endhint %}
To delete a node pool, follow these steps:
1. In the **DCD**, go to **Menu** > **Containers** > **Managed Kubernetes**.
2. Select a cluster from the list and go to the **Node pools** tab.
3. Select the node pool you want to delete.
4. Select **Node pool settings**.
5. Select **Delete node pool**. Optionally, open the node pool by selecting the **name**, and select the  next to the node pool's name and choose **Delete node pool**.
6. In the confirmation dialog, select **Delete**.
{% hint style="success" %}
**Result:** Managed Kubernetes will remove the resources from the target data center and the node pool is successfully deleted.
{% endhint %}
---
# 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.ionos.com/cloud/containers/managed-kubernetes/how-tos/delete-node-pool.md?ask=&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.