Why doesn't replacing a worker node create a worker node?

Troubleshoot worker node autorebalancing issues.

Virtual Private Cloud Classic infrastructure Satellite

When you replace a worker node or update a VPC worker node, a worker node is not automatically added back to your cluster.

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.

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 ks 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 maintain a worker node using one of the following commands, but no additional worker node is created to replace it.
   • Classic bare metal workers: ibmcloud ks worker reload reloads the worker in place (no deletion or addition). ibmcloud ks worker update moves the worker to the master BOM version.
   • VPC workers: ibmcloud ks worker replace --update deletes the existing worker and provisions a new one at the master version. ibmcloud ks worker replace does the same at the current patch version. Note that ibmcloud ks worker update is not supported for VPC worker nodes.

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.

To enable automatic rebalancing, rebalance or resize your worker pool. Now, when you replace a worker node, another worker node is created for you.