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 Jobs. Specifically for the Job Delete operation, it enables deleting a Job resource within a specified cluster, project, and namespace.
Typical use cases include:
- Automating cleanup of completed or failed jobs in a Kubernetes environment.
- Managing job lifecycle as part of CI/CD pipelines or scheduled maintenance workflows.
- Integrating Kubernetes job management into broader automation workflows without manual intervention.
For example, you can configure this node to delete a specific Job by selecting the cluster, project, and namespace where the Job resides, then specifying the Job ID to remove it programmatically.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the Job exists. 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. Choose from a list or specify an ID via expression. |
These properties define the scope (cluster, project, namespace) in which the Job resource is managed.
Output
The node outputs JSON data representing the result of the delete operation on the Job resource. Typically, this will be confirmation details or status information returned by the Rancher/Kubernetes API after the deletion request.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Rancher or Kubernetes API endpoint.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node depends on dynamic loading methods to populate options for clusters, projects, and namespaces.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection may cause the operation to fail.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Specifying a non-existent Job ID will result in a "not found" error from the API.
Error messages:
- "Unauthorized" or "Forbidden": Check that the API key or token has sufficient rights.
- "Job not found": Verify the Job ID and ensure it exists in the selected namespace.
- Timeouts or network errors: Confirm connectivity to the Rancher/Kubernetes API server.
Resolving these typically involves verifying input parameters, ensuring correct API credentials, and confirming resource existence.
Links and References
- Rancher API Documentation
- Kubernetes Jobs API Reference
- n8n Expressions Documentation (for using expressions in property fields)