kubernetes.node.cordon

Mark a Node as unschedulable (kubectl cordon equivalent)

Marks a Kubernetes Node as unschedulable by setting spec.unschedulable: true, equivalent to kubectl cordon <node>. The operation is idempotent: cordoning an already-cordoned node succeeds silently.

Inputs:

• connection_uuid: Cloud connection UUID (required)
• name: Node name (required)

Outputs:

• previously_schedulable: True if the node was schedulable before this call, False if it was already cordoned.

Plugin required: context.get_plugin("connection").kubernetes_runner_clients(connection_uuid, organization_uuid) must expose core_v1 (a CoreV1Api instance) with read_node and patch_node.

Overview

Property	Value
Workflow type	Atomic
Library	App-kubernetes
Version	1.0

Input Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	Yes	—	—
name	string	Yes	—	—
organization_uuid	uuid	No	—	—

Output Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	No	—	—
organization_uuid	uuid	No	—	—
name	string	No	—	—
previously_schedulable	boolean	No	—	—
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_at_state	string	No	—	—
failed_step	string	No	—	—
failed_layer	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	execute	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
pending	execute	completed	—
* (any state)	fail	failed	—

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "kubernetes.node.cordon",
  "initial_data": {
    "connection_uuid": "value",
    "name": "value"
  }
}