Actions54
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
- Node Actions
- Workload Actions
Overview
This node allows users to interact with Rancher and Kubernetes APIs to manage various Kubernetes resources, including CronJobs. Specifically for the CronJob Delete operation, it enables deleting a specified CronJob resource within a Kubernetes cluster managed by Rancher.
Typical use cases include:
- Automating cleanup of scheduled jobs that are no longer needed.
- Managing lifecycle of batch jobs in Kubernetes environments.
- Integrating Kubernetes job management into broader automation workflows.
For example, you might use this node to delete a CronJob after a project phase ends or when a scheduled task is deprecated.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the CronJob resides. You can choose from a list or specify an ID via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Choose from a list or specify an ID via expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project where the CronJob exists. Choose from a list or specify an ID via expression. |
These properties identify the exact location of the CronJob resource to be deleted.
Output
The node outputs JSON data representing the result of the delete operation. This typically includes confirmation details or status information returned by the Rancher/Kubernetes API about the deletion of the CronJob.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Rancher-managed Kubernetes cluster.
- Needs an API authentication token or API key credential configured in n8n to authenticate requests to the Rancher/Kubernetes API.
- The node depends on dynamic loading methods to populate options for clusters, projects, and namespaces.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace identifiers may cause the node to fail to locate the CronJob.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Attempting to delete a non-existent CronJob will result in an error from the Kubernetes API.
Error messages:
- "Resource not found" — Verify that the CronJob ID and namespace are correct.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
- "Failed to connect" — Ensure network connectivity to the Rancher API endpoint.
Resolving these usually involves verifying input parameters, ensuring proper API credentials, and confirming access rights.
Links and References
- Kubernetes CronJob Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)