Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node integrates with the Rancher/Kubernetes API to manage Kubernetes resources programmatically within n8n workflows. Specifically, for the Node resource and the Uncordon operation, it marks a Kubernetes node as schedulable again after it was previously marked unschedulable (cordoned). This is useful in scenarios where maintenance or updates on a node are complete, and you want to allow new pods to be scheduled on that node.
Practical examples include:
- After performing system updates or hardware maintenance on a Kubernetes node, use this node to uncordon the node so workloads can resume scheduling.
- Automate cluster management by cordoning nodes before draining them and then uncordoning once maintenance tasks finish.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the node resides. Choose from the list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. Choose from the list or specify an ID via expression. |
| Namespace Name or ID | Select the namespace within the project. Depends on the selected project. Choose from the list or specify an ID via expression. |
| Node ID | The unique identifier of the node to uncordon. Required to specify which node to mark as schedulable. |
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 access to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on dynamic loading of clusters, projects, and namespaces via internal methods to populate dropdown options.
Troubleshooting
Common issues:
- Incorrect or missing Node ID will cause the operation to fail because the target node cannot be identified.
- Insufficient permissions or invalid API credentials may lead to authorization errors.
- Specifying a cluster, project, or namespace that does not contain the node will result in errors or empty responses.
Error messages:
- "Node not found" — Verify the Node ID and ensure it exists in the selected cluster/project/namespace.
- "Unauthorized" or "Forbidden" — Check API credentials and permissions.
- "Invalid parameters" — Confirm all required properties are correctly set, especially Node ID and cluster selection.
Resolving these usually involves verifying input parameters, ensuring correct API credentials, and confirming the node's existence in the specified context.