Recycling a Node Pool instance in a Vultr Kubernetes Engine (VKE) cluster replaces a specific node with a fresh instance of the same configuration, which resolves node-level issues, applies updates, or recovers from resource constraints without disrupting the entire Node Pool. Recycle performs a surge replacement. VKE provisions the replacement node and waits for it to join the cluster before draining and removing the target node, so the Node Pool temporarily runs one node above its configured size.
Recycling a node deletes the target instance after the replacement joins the cluster. Any ephemeral data, logs, or local configurations on that instance are lost. Draining reschedules workloads onto the replacement node or other available nodes. Linked resources remain attached, but if the node was part of a Load Balancer backend, brief downtime can occur while the new node registers. To prevent data loss, store important data in Persistent Volumes or external storage, or back it up before recycling.
Follow this guide to recycle a Node in a Vultr Kubernetes Engine cluster on your Vultr account using the Vultr Console, API, or CLI.
0 Comments
Be the first to comment and share your perspective with the community.