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 Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically within n8n workflows. Specifically, for the CronJob resource with the Suspend operation, it allows users to suspend a scheduled CronJob in a Kubernetes cluster. Suspending a CronJob temporarily stops it from triggering new jobs without deleting the CronJob itself.
Typical use cases include:
- Temporarily pausing scheduled tasks during maintenance windows.
- Preventing execution of periodic jobs when debugging or updating related systems.
- Controlling job execution dynamically based on workflow logic.
Example: You have a CronJob that runs database backups every night. Using this node, you can suspend the CronJob during a system upgrade to avoid conflicts.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the CronJob resides. Choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. Choose from a list or specify an ID. |
| Namespace Name or ID | Select the namespace containing the CronJob. Depends on the selected project. Choose from a list or specify an ID. |
These properties are required to identify the exact CronJob resource to suspend.
Output
The node outputs JSON data representing the result of the suspend operation on the specified CronJob. This typically includes the updated state of the CronJob resource as returned by the Rancher/Kubernetes API, confirming that the CronJob is now suspended.
No binary data output is involved.
Dependencies
- Requires access to a Rancher or Kubernetes cluster API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node depends on internal methods to load options for clusters, projects, and namespaces dynamically.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection leading to resource not found errors.
- Insufficient permissions or invalid API credentials causing authorization failures.
- Network connectivity problems to the Kubernetes API endpoint.
Error messages:
- "Resource not found" — Verify that the cluster, project, namespace, and CronJob exist and are correctly specified.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
- Timeout or connection errors — Ensure network access to the Kubernetes API server.
Resolving these usually involves verifying configuration details, credentials, and network settings.
Links and References
- Kubernetes CronJob Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)