Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
CronJobs → Logs
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on Kubernetes resources, specifically supporting the 'Logs' operation for CronJobs in this context. It retrieves logs from a specified container within a CronJob resource in a given namespace. This is useful for monitoring and debugging CronJobs by accessing their output logs directly within an automation workflow.
Use Case Examples
- Fetching logs from a specific container of a CronJob to monitor scheduled task execution and troubleshoot issues.
- Automating log retrieval for CronJobs to integrate with centralized logging or alerting systems.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the CronJob resource is located. |
| Resource Name | The name of the specific CronJob resource to retrieve logs from. |
| Container Name | The name of the container within the CronJob from which to fetch logs. |
Output
JSON
logs- The logs output from the specified container of the CronJob resource.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure that the Kubernetes credentials provided have sufficient permissions to access the specified namespace and CronJob resource.
- Verify that the resource name and container name are correct and exist in the specified namespace to avoid errors.
- Common error: 'Resource name is required for logs operation!' indicates that the resourceName parameter was not provided; ensure it is set correctly.