Actions90
- Jobs Actions
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- CronJobs Actions
Overview
This node interacts with Kubernetes Jobs to retrieve their logs. It is useful for monitoring and debugging batch jobs running in a Kubernetes cluster by fetching the output logs of specific Job resources. For example, after triggering a Job that processes data or runs a batch task, you can use this node to fetch its logs and verify execution results or diagnose issues.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the Job resource resides. Defaults to "default". |
| Resource Name | The name of the specific Job resource whose logs you want to retrieve. |
Output
The node outputs JSON data containing the logs of the specified Job resource. The exact structure depends on the Kubernetes API response but generally includes log text or structured log entries related to the Job's pods. This output allows further processing or inspection within an n8n workflow.
Dependencies
- Requires valid Kubernetes API credentials configured in n8n to authenticate and communicate with the Kubernetes cluster.
- Depends on the Kubernetes API being accessible and the specified Job existing in the given namespace.
Troubleshooting
- No credentials got returned!: Indicates missing or misconfigured Kubernetes API credentials. Ensure credentials are properly set up in n8n.
- Resource not found or empty logs: Verify that the Job name and namespace are correct and that the Job has generated logs.
- Command must be an array!: Although not directly related to logs operation, this error may appear if other operations like "run" are used incorrectly. Make sure commands are provided as arrays when required.