---
name: openshift-ts-worker-autorebalance
title: Why doesn't replacing a worker node create a worker node?
description: '[Virtual Private Cloud] [Classic infrastructure] [Satellite]'
last-updated: 2026-07-30
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why doesn't replacing a worker node create a worker node?
{: #auto-rebalance-off}
{: support}


[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf} [Satellite]{: tag-satellite}


When you [replace a worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli&format=markdown#worker-replace-cli) or [update a VPC worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-update&format=markdown#vpc_worker_node), a worker node is not automatically added back to your cluster.
{: tsSymptoms}


By default, your worker pools are set to automatically rebalance when you replace a worker node. However, you might have disabled automatic rebalancing by manually removing a worker node, such as in the following scenario.
{: tsCauses}

1. You have a worker pool that automatically rebalances by default.
2. You have a troublesome worker node in the worker pool that you removed individually, such as with the `ibmcloud oc worker rm` command.
3. Now, automatic rebalancing is disabled for your worker pool, and is not reset unless you try to rebalance or resize the worker pool.
4. You try to replace a worker node with the `ibmcloud oc worker replace` command or update a VPC worker node with the `ibmcloud oc worker replace --update` command. The worker node is removed, but another worker node is not added back to your worker pool.

You might also have issued the `remove` command shortly after the `replace` command. If the `remove` command is processed before the `replace` command, the worker pool automatic rebalancing is still disabled, so your worker node is not replaced.
{: note}

To enable automatic rebalancing, [rebalance](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli&format=markdown#worker-pool-rebalance-cli) or [resize](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli&format=markdown#worker-pool-resize-cli) your worker pool. Now, when you replace a worker node, another worker node is created for you.
{: tsResolve}