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 Create operation, it allows users to create a new Kubernetes Job in a specified cluster, project, and namespace.
Use cases include automating batch job creation in Kubernetes clusters, such as running data processing tasks, scheduled jobs, or any containerized workload that needs to be executed once or on-demand.
Example: Automatically trigger a Kubernetes Job to process uploaded files whenever a new file arrives in a storage bucket.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the Job will be created. Can choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the chosen cluster. Options depend on the selected cluster. |
| Namespace Name or ID | Select the namespace within the project where the Job will be created. Options depend on the selected project. |
These properties are required to scope the Job creation to the correct Kubernetes environment.
Output
The node outputs JSON data representing the response from the Rancher/Kubernetes API after creating the Job. This typically includes metadata about the created Job resource such as its name, status, and other Kubernetes Job details.
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 Rancher/Kubernetes API availability and proper permissions to create Jobs in the specified cluster/project/namespace.
- The node uses internal methods to load options dynamically for clusters, projects, and namespaces.
Troubleshooting
- Common issues:
- Invalid or missing cluster/project/namespace IDs can cause failures.
- Insufficient permissions in the Kubernetes cluster to create Jobs.
- Network connectivity issues to the Rancher/Kubernetes API endpoint.
- Error messages:
- Authentication errors indicate problems with the API credentials.
- "Resource not found" errors suggest incorrect cluster/project/namespace selection.
- Validation errors may occur if required parameters (like Job spec) are incomplete or malformed.
- Resolutions:
- Verify API credentials and permissions.
- Confirm cluster, project, and namespace selections are correct.
- Ensure all required input fields are provided and valid.
Links and References
- Kubernetes Jobs Documentation
- Rancher API Reference
- n8n Expressions Documentation (for dynamic parameter values)