Actions54
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
- Node Actions
- Workload Actions
Overview
The node provides integration with Rancher and Kubernetes APIs, allowing users to manage various Kubernetes resources programmatically within n8n workflows. Specifically for the Node resource with the Uncordon operation, this node marks a previously cordoned (unschedulable) Kubernetes node as schedulable again. This means the node will be available to schedule new pods.
This operation is useful in scenarios such as:
- After maintenance or troubleshooting on a node, you want to bring it back into the cluster's scheduling pool.
- Automating cluster management workflows where nodes are dynamically cordoned and uncordoned based on load or health checks.
Example use case:
- A workflow that drains a node for maintenance, performs updates, then automatically uncordons the node to resume normal operations.
Properties
| Name | Meaning |
|---|---|
| Node ID | The unique identifier of the Kubernetes node to uncordon (make schedulable). |
| Cluster Name or ID | Select or specify the target Kubernetes cluster where the node resides. |
| Project Name or ID | (Optional) Select or specify the project within the cluster context. |
| Namespace Name or ID | (Optional) Select or specify the namespace within the project context. |
Output
The node outputs JSON data representing the result of the uncordon operation on the specified node. This typically includes the updated node object or status information returned by the Rancher/Kubernetes API confirming the node is now schedulable.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Rancher or Kubernetes cluster via an API key credential configured in n8n.
- The node depends on Rancher's or Kubernetes' API endpoints to perform node management actions.
- Proper permissions are required on the API token to modify node scheduling states.
Troubleshooting
Common issues:
- Invalid or missing Node ID: Ensure the Node ID corresponds to an existing node in the selected cluster.
- Insufficient permissions: The API token must have rights to update node conditions.
- Network or connectivity errors: Verify that the Rancher/Kubernetes API endpoint is reachable from n8n.
Error messages:
- "Node not found" — Check the Node ID and cluster selection.
- "Unauthorized" or "Forbidden" — Confirm API credentials have sufficient privileges.
- Timeout or connection refused — Validate network access and API server availability.
Resolving these usually involves verifying input parameters, credentials, and network configurations.