> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply Node Pool updates

> Apply Node Pool updates by queuing a reconfigure reboot

This page describes how to apply Node Pool updates by queuing a reconfigure reboot. Follow this procedure when you need to roll out an updated Node Pool configuration, such as a new system OS image or GPU driver, to existing Nodes in a CoreWeave Kubernetes Service (CKS) cluster.

You can manually reboot Nodes in two ways:

* **Standard Node reboot**: A typical reboot to apply a system update or other change.
* **Reconfigure reboot**: A reboot to apply an updated Node Pool configuration to existing Nodes.

Some Node Pool modifications require you to both reconfigure and reboot the Nodes to apply updates, for example, a new system OS image or GPU driver update. See [Manage Node Pool configuration](/products/cks/nodes/manage#manage-node-pool-configuration) for more details.

To apply these updates, you can queue a reconfigure reboot for the necessary Nodes. If you need to reboot Nodes manually to apply a system update or other change, without reconfiguring the Node, see [Reboot Nodes](/products/cks/nodes/reboot).

## Prerequisites

Before you begin, ensure you have:

* An active CoreWeave account.
* An [API Access Token](/security/authn-authz/managed-auth/api-access).
* The [CoreWeave Intelligent CLI](https://github.com/coreweave/cwic) installed locally.

## Queue a reconfigure reboot

To queue a reconfigure reboot for a Node Pool, use the `cwic node reboot` command with the `--reconfigure` flag. Replace `[NODE-NAMES]` with a space-separated list of the Nodes you want to reboot:

```bash theme={"system"}
cwic node reboot --reconfigure [NODE-NAMES]
```

When you submit the command, it queues a reconfigure reboot to begin as soon as the Nodes are
idle. Meanwhile, CoreWeave cordons the Nodes to prevent scheduling new workloads.

The reconfiguration and reboot process can take up to an hour:

* During the reconfiguration and reboot, the Node `PhaseState` condition moves to
  `production-reconfigure-powercycle-test`, and the Node becomes unavailable.
* When the reconfiguration is complete, the Node `PhaseState` condition returns to `production` and the Node is uncordoned.

<Warning>
  **Reboot Nodes in small batches**

  When you reboot Nodes, limit the number of Nodes you reboot at one time to avoid service interruptions. If you need to reboot 50 or more Nodes at a time, [contact support for assistance](/support).
</Warning>

Once the reconfigure reboot completes for each Node, the updated Node Pool configuration is applied and the Node returns to service.

### Optional flags

The following sections describe two optional `cwic` flags you can use to expedite the total reboot time. Use `--no-test` to skip post-reboot validation, and `--force` to queue the reboot to begin immediately.

#### Skip post-reboot validation

CoreWeave performs a post-reboot validation of a Node after any reboot to ensure it operates within acceptable tolerances. This test usually takes about 30 minutes of the overall reboot time. To expedite reboots, you can skip the validation by using the `--no-test` flag. This sets the Node `PhaseState` to
`production-reconfigure-powerreset`.

#### Queue reboot to start immediately

You can queue a reconfigure reboot to begin immediately by adding the `--force` flag, but this flag doesn't consider the active state of the Nodes. Before you use this flag, ensure the Nodes are idle or otherwise able to interrupt running workflows.