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 CronJob resource with the Resume operation, this node resumes a suspended CronJob in a Kubernetes cluster managed by Rancher.
This is useful in scenarios where scheduled jobs (CronJobs) have been paused or suspended and need to be restarted without recreating them. For example, you might suspend a CronJob during maintenance windows and then resume it afterward automatically using this node.
Practical examples:
- Automatically resume a CronJob after a deployment or system update.
- Resume scheduled batch jobs that were temporarily suspended due to resource constraints.
- Control CronJob execution flow dynamically based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the CronJob resides. Can choose from a list or specify an ID via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Depends on the selected cluster. |
| Namespace Name or ID | (Optional) Select the namespace containing the CronJob. Depends on the selected project. |
These properties are used to identify the exact CronJob resource to operate on within the Rancher/Kubernetes environment.
Output
The node outputs JSON data representing the result of the resume operation on the specified CronJob. This typically includes the updated state of the CronJob resource as returned by the Rancher/Kubernetes API after resuming it.
No binary data output is involved.
Dependencies
- Requires access to a Rancher-managed Kubernetes cluster.
- Needs an API authentication credential configured in n8n to connect securely to the Rancher API.
- The node depends on internal methods to load options for clusters, projects, and namespaces dynamically.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace identifiers can cause failures in locating the CronJob.
- Insufficient permissions or invalid API credentials may lead to authorization errors.
- Attempting to resume a CronJob that is not suspended or does not exist will likely return an error.
Error messages and resolutions:
- "Resource not found" — Verify that the cluster, project, namespace, and CronJob IDs are correct.
- "Unauthorized" or "Forbidden" — Check API credentials and ensure they have sufficient permissions.
- "Operation not allowed" — Confirm that the CronJob is currently suspended and can be resumed.
Links and References
- Kubernetes CronJob Documentation
- Rancher API Reference
- n8n Expressions Documentation (for dynamic property values)