# Can I resize a DOKS node?

DOKS nodes inherit their sizing and capacity properties from their node pool, and you cannot change node pool settings after creation.

To increase the amount of resources your nodes have, you need to [create a new node pool](https://docs.digitalocean.com/products/kubernetes/getting-started/quickstart/index.html.md#edit-nodes-and-node-pools-for-an-existing-cluster) of the desired size. After you have created the new node pool and it displays a ‘Ready’ status, delete the older smaller node pool. This causes the workloads on the old node pool to get rescheduled on the new larger nodes.

This does not incur downtime as long as your applications are deployed in a highly available manner with multiple [replicas](https://docs.digitalocean.com/products/kubernetes/concepts/best-practices/index.html.md#use-replicas-instead-of-bare-pods) and [appropriately sized nodes](https://docs.digitalocean.com/products/kubernetes/concepts/best-practices/index.html.md#size-nodes-pools-for-high-availability).

## Related Topics

[Why is my resized volume smaller than I expected?](https://docs.digitalocean.com/support/why-is-my-resized-volume-smaller-than-i-expected/index.html.md): Differences in filesystem overhead, reserved space, and unit conversions can make a resized volume appear smaller than its allocated size.

[Can I make my Droplet smaller?](https://docs.digitalocean.com/support/can-i-make-my-droplet-smaller/index.html.md): You cannot resize Droplets to smaller plans, but you can migrate your data to a smaller Droplet.

[How to Troubleshoot CoreDNS Issues in DOKS Clusters](https://docs.digitalocean.com/support/how-to-troubleshoot-coredns-issues-in-doks-clusters/index.html.md): Gather information to resolve CoreDNS-related DNS problems in DOKS clusters.