> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/knowledge-base/system-administration/removing-a-node-from-cluster.md).

# Removing a Node from a VergeOS Cluster

## Overview

This guide covers the process of removing a physical node from a VergeOS system. This procedure is used for hardware decommissioning, cluster downsizing, or node replacement scenarios.

{% hint style="warning" %}
**Important Limitation**

Node removal can only be performed on the **last node** in the system. Nodes must be removed in reverse order (last added, first removed).
{% endhint %}

## Prerequisites

Before removing a node, ensure the following:

* **vSAN Health**: All vSAN tiers must be healthy (green status)
* **Cluster Size**: At least two nodes must remain in the cluster after removal
* **Recent Snapshot**: A current system snapshot is recommended before proceeding
* **Backup Access**: Verify IPMI or console access is available for troubleshooting

## Removal Process

### Step 1: Enable Maintenance Mode

1. Navigate to **System** > **Nodes**.
2. Double-click the **last node** in the system.
3. Click **Enable Maintenance** on the left menu.
4. Click **Yes** to confirm.
5. Wait for all workloads to migrate off the node. Monitor the **Running Machines** section until it is empty.

{% hint style="info" %}
**Non-Migratable Workloads**

VMs with GPU passthrough or host CPU type must be powered off manually before the node can enter maintenance mode.
{% endhint %}

### Step 2: Offline and Delete Drives

Before powering off the node, all drives must be removed from the vSAN.

1. From the node's dashboard, click **Drives** on the left menu.
2. Select all drives listed for the node.
3. Click **Offline** from the action menu.
4. Click **Yes** to confirm.
5. Wait for all drives to show **Offline** status.
6. With all drives still selected, click **Delete** from the action menu.
7. Click **Yes** to confirm the deletion.

{% hint style="warning" %}
**Wait for Data Migration**

After deleting the drives, the vSAN will migrate data to remaining drives. Monitor the vSAN dashboard and wait for repairs to complete before proceeding to the next step.
{% endhint %}

### Step 3: Power Off the Node

{% hint style="danger" %}
**Verify vSAN Health Before Proceeding**

Before powering off the node, navigate to **Infrastructure** > **vSAN Tiers** and confirm all tiers are **green** (healthy). Do not proceed until the vSAN has fully recovered from the drive removal in Step 2.
{% endhint %}

1. Once all drives are deleted and the node status shows **Maintenance Mode**, click **Power Off** on the left menu.
2. Click **Yes** to confirm.
3. Wait for the node to fully power down.

### Step 4: Delete the Node

1. With the node powered off, click **Delete** on the left menu.
2. Click **Yes** to confirm the deletion.

### Step 5: Wait for Final Repairs

After the node is deleted, the vSAN will perform final data redistribution across the remaining nodes.

1. Navigate to **System** > **vSAN** to monitor repair progress.
2. Wait for all tiers to return to **green** (healthy) status before performing any other operations.

{% hint style="danger" %}
**Do Not Interrupt Repairs**

Do not power off, restart, or remove additional nodes while vSAN repairs are in progress. Allow the repairs to complete fully.
{% endhint %}

## Post-Removal Verification

After repairs complete:

* Verify all vSAN tiers show green status
* Confirm cluster resources are balanced across remaining nodes
* Check system logs for any warnings or errors

## Additional Resources

* [Maintenance Mode](/run-the-platform/operations/maintenance-mode.md)
* [Nodes Overview](/run-the-platform/system-administration/nodes-overview.md)
* [Clusters Overview](/run-the-platform/system-administration/clusters-overview.md)


---

# 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 current page URL with the `ask` query parameter:

```
GET https://docs.vergeos-demo.com/knowledge-base/system-administration/removing-a-node-from-cluster.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.