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 interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources, including CronJobs. Specifically, for the CronJob Create operation, it enables users to create a new scheduled job (CronJob) within a specified Kubernetes cluster environment.
Use cases include automating repetitive tasks in Kubernetes clusters, such as running backups, sending reports, or performing maintenance jobs on a schedule. For example, you could use this node to create a CronJob that runs a database backup script every night at midnight.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the CronJob will be created. Choose from the list or specify an ID via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Choose from the list or specify an ID via expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project where the CronJob will be created. Choose from the list or specify an ID via expression. |
These properties define the target environment for the CronJob creation.
Output
The node outputs JSON data representing the result of the CronJob creation API call. This typically includes details about the newly created CronJob resource, such as its metadata, specification, status, and identifiers assigned by the Kubernetes system.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Requires an API authentication token or key configured in n8n credentials 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 IDs can cause failures.
- Insufficient permissions or invalid API credentials may lead to authorization errors.
- Network connectivity problems to the Kubernetes API server can cause timeouts or connection errors.
Error messages:
- Authorization errors usually indicate invalid or missing API keys; verify credentials.
- Resource not found errors suggest incorrect cluster/project/namespace selections.
- Validation errors may occur if required fields are missing or malformed.
Resolving these typically involves verifying input parameters, ensuring correct credential setup, and confirming network access to the Kubernetes API.
Links and References
- Kubernetes CronJob Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property values)