How to remove an existing additional MachinePool from ROSA/OSD cluster

Solution Verified - Updated 2024-06-13T18:42:00+00:00 -

English

• No translations currently exist.

Environment

• OpenShift Dedicated
• Red Hat OpenShift Service on AWS

Issue

• You want to remove your additional MachinePool from your ROSA/OSD cluster due to some reason.
• You should remove your additional MachinePool before expiration date of additional worker node subscription on your OSD cluster.

Resolution

• After scaling in as 0 worker node first using OCM, please remove the existing MachinePool for draining and evicting gracefully the running workloads on the nodes.
• You should have the remained node resources enough to accommodate the draining workloads from the removed worker nodes.

Root Cause

• If you remove the additional MachinePool without scaling in as 0, the node can be removed without draining and re-scheduling the existing workloads.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.