Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node integrates with the Rancher/Kubernetes API to manage various Kubernetes resources, including CronJobs. Specifically, for the CronJob - Get operation, it retrieves information about one or more CronJobs within a specified Kubernetes namespace. This is useful for monitoring scheduled jobs, auditing their configurations, or triggering workflows based on their status.
Common scenarios include:
- Fetching details of existing CronJobs to verify schedules and job templates.
- Automating checks on CronJob statuses before running dependent processes.
- Integrating Kubernetes CronJob data into broader automation pipelines.
Example: You might use this node to get all CronJobs in a particular namespace to list their schedules and last run times, then send notifications if any are failing.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the CronJob resides. Can be chosen from a list or specified via an expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. Can be chosen from a list or specified via expression. |
| Namespace Name or ID | Select the namespace within the project where the CronJob exists. Can be chosen from a list or specified via expression. |
These properties are required to scope the request correctly to the desired CronJob resource.
Output
The node outputs JSON data representing the retrieved CronJob(s). The structure corresponds to the Kubernetes API response for CronJobs, typically including fields such as:
- Metadata (name, namespace, labels, annotations)
- Spec (schedule, job template, concurrency policy)
- Status (last schedule time, active jobs, conditions)
The output is an array of JSON objects, each representing a CronJob matching the query parameters.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Needs 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
- Missing or incorrect cluster/project/namespace selection: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- Authentication errors: Verify that the API key or token has sufficient permissions to read CronJob resources.
- Empty results: Confirm that there are CronJobs deployed in the specified namespace.
- API connectivity issues: Check network access to the Kubernetes/Rancher API endpoint.
Common error messages may include authorization failures or resource not found errors, which usually indicate misconfiguration of credentials or incorrect property values.
Links and References
- Kubernetes CronJob API Reference
- Rancher API Documentation
- n8n Expressions Documentation (for using expressions in property fields)