Uncordon node
uncordon_nodeUncordon one Kubernetes node: set spec.unschedulable=false so new pods can schedule onto it again. The reversal of cordon_node - use it when a cordoned node should return to service (e.g. a consolidation was abandoned, or maintenance finished). node_name must match the Kubernetes node name exactly (call get_nodes to list them); an unknown node is refused without changing anything.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"node_name": "<node_name>",
"cluster_id": "<cluster_id>"
},
"name": "uncordon_node"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dry_run | No | If true, preview the change without executing it. | |
| node_name | Yes | Exact name of the Kubernetes node to uncordon (from get_nodes). | |
| cluster_id | Yes | Ankra cluster id (UUID) the call targets. Discover ids with list_clusters. |