Unassign Machine
Machines assigned to a Machine Pool can be unassigned and reused for different Machine Pool / Clusters. The unassignment will gracefully remove the Machine from its Kubernetes cluster and drain the deployed resources.
WARNING
Before unassigning Machines, make sure to verify the cluster's healthiness and capacity.
- Go to Machines → your machine → edit
- Under Machine Pool, select No Machine Pool
- Click Preview to review the change, then Roll out to immediately start the unassignment. Alternatively, save the revision and roll it out later.
Force Remove from Pool
If a Machine is non-responsive or orphaned, you can force-remove it from its Machine Pool.
- Go to Machines → your machine
- Click Actions → Force Remove From Pool
WARNING
Force-removing a Machine skips the graceful drain. The node is deleted from the Kubernetes cluster immediately, and workloads running on it are left in an orphaned state.
Force removal:
- Deletes the node from the Kubernetes cluster
- Cancels any in-flight operations
- Sets the Machine status to force_unassigned
- Triggers a revision rollout. If the melt-agent is still running (or comes back online), the Machine reboots and transitions to ready_unassigned, making it available for reassignment
TIP
After force-removing, the Machine is not deleted. It stays registered and can be reassigned once it reaches ready_unassigned. To fully remove it, delete the Machine after force removal.