Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node enables interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically within n8n workflows. Specifically, for the Job resource with the Delete operation, it allows users to delete a Kubernetes Job from a specified namespace within a project and cluster.
Common scenarios where this node is beneficial include:
- Automating cleanup of completed or failed Kubernetes Jobs.
- Managing lifecycle of batch processing tasks in Kubernetes clusters.
- Integrating Kubernetes job management into broader automation workflows.
For example, you can use this node to delete a Job after its successful completion to free up cluster resources automatically.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the Job exists. Choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster that contains the Job. Depends on the selected cluster. |
| Namespace Name or ID | Select the namespace within the project where the Job resides. Depends on the selected project. |
These properties are required to precisely identify the Job resource to delete.
Output
The node outputs JSON data representing the response from the Rancher/Kubernetes API after attempting to delete the Job. This typically includes status information about the deletion request.
The output structure is an array with one element per input item, each containing a json field with the API response.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the Rancher/Kubernetes API.
- The node depends on dynamic loading methods to populate options for clusters, projects, and namespaces.
- Proper permissions on the Kubernetes cluster are necessary to delete Jobs.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection leading to "resource not found" errors.
- Insufficient permissions to delete Jobs causing authorization errors.
- Network connectivity problems to the Rancher/Kubernetes API endpoint.
Error messages and resolutions:
- "Not Found" — Verify that the cluster, project, namespace, and Job exist and are correctly specified.
- "Forbidden" or "Unauthorized" — Check API credentials and user permissions.
- Timeouts or connection errors — Ensure network access to the Rancher/Kubernetes API and correct endpoint configuration.
Links and References
- Kubernetes Jobs Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)