Skip to main content
DELETE
Remove a node from a node group of a HPE Morpheus cluster

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

authorization
string | null
x-ankra-organisation-id
string | null

Path Parameters

cluster_id
string<uuid>
required
group_name
string
required
node
string
required

The worker to remove: its node id, its server name, its Kubernetes node name, or the providerID its node reports with its slashes escaped as %2F. Matched case-insensitively.

Query Parameters

force_drain
boolean
default:false

Take the worker down on a cluster teardown's drain, without honouring PodDisruptionBudgets. Off by default: the worker is drained through its budgets, and a refused drain keeps the worker and the group's count and fails the operation naming what refused it.

wait
boolean
default:false

Response

The worker is being removed (wait=true)

group_name
string
required
node_name
string
required

The server name of the removed worker, as the node group's node list shows it. It is not always the name of its Kubernetes node: that is kubernetes_node_name.

kubernetes_node_name
string | null
required

The name of the Kubernetes node the removed worker registered as: its lowercased server name on every provider but AWS, where it is the EC2 private DNS name the platform records once the instance exists. Null while that is not recorded yet.

node_id
string<uuid>
required

The node id of the removed worker.

previous_count
integer
required

The group's node count before the removal.

new_count
integer
required

The group's node count once the worker is gone.

operation_id
string<uuid> | null
required

The operation draining and deleting the worker, followed on /api/v1/org/executions/{execution_id}. Null when the request created none: the removal is saved and the platform's reconcile dispatches it, because the request could not start the operation itself: another operation is still changing a node of the cluster, or a reconcile pass holds the cluster's dispatch; the cluster is inside a force-stop admission window; the work waits for the cluster's agent, which is offline; the re-planned deletes are held to their retry backoff; or creating the operation failed.