node_management
Destructive
Cordon, drain, or uncordon Kubernetes nodes to control scheduling and safely remove workloads for maintenance.
Instructions
Manage Kubernetes nodes with cordon, drain, and uncordon operations
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": {
"operation": "<operation>"
},
"name": "node_management"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Force the operation even if there are pods not managed by a ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet (for drain operation) | |
| dryRun | No | Show what would be done without actually doing it (for drain operation) | |
| timeout | No | The length of time to wait before giving up (for drain operation, e.g., '5m', '1h') | 0 |
| nodeName | No | Name of the node to operate on (required for cordon, drain, uncordon) | |
| operation | Yes | Node operation to perform | |
| gracePeriod | No | Period of time in seconds given to each pod to terminate gracefully (for drain operation). If set to -1, uses the kubectl default grace period. | |
| confirmDrain | No | Explicit confirmation to drain the node (required for drain operation) | |
| deleteLocalData | No | Delete local data even if emptyDir volumes are used (for drain operation) | |
| ignoreDaemonsets | No | Ignore DaemonSet-managed pods (for drain operation) |