> 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.7/nodes/detach-node-from-cluster.md).

# Detach Node From Cluster

Nodes that are attached to an on-premises Kubernetes cluster created using PMK can be detached when the nodes are not required to be a part of the cluster.

When you detach a node, the containers running on the node are destroyed. Pods that are associated with the Replication Controller or Deployment are automatically restarted by Kubernetes on another node in the cluster, if sufficient resources are available.

You can detach nodes from the Infrastructure -> Clusters tab.

Detach Nodes from Clusters tab

Follow the steps below to detach a node from a cluster.

1. Navigate to Infrastructure > Clusters.
2. Select the cluster from which you wish to detach a node.
3. Select Scale Masters or Scale Workers
4. Select the node or nodes to detach.
5. Click Detach Node and confirm detachment.

To fully remove a node from PMK, you need to first detach it from a cluster and then [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/kubernetes/deauthorize-node/README.md) the node.


---

# 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.7/nodes/detach-node-from-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.