Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Services → Logs
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on Kubernetes resources, specifically focusing on the 'Services' resource with the 'Logs' operation in this context. It retrieves logs from a specified container within a Kubernetes service, which is useful for monitoring and debugging applications running in Kubernetes clusters. For example, a user can fetch logs from a service's main container to diagnose issues or verify application behavior.
Use Case Examples
- Fetching logs from a specific container in a Kubernetes service to monitor application output or troubleshoot errors.
- Retrieving logs from the 'main-container' of a service named 'my-service' in the 'default' namespace.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the service is located. Defaults to 'default' if not specified. |
| Resource Name | The name of the Kubernetes service resource from which to retrieve logs. |
| Container Name | The name of the container within the service to fetch logs from. Defaults to 'main-container'. |
Output
JSON
logs- The logs retrieved from the specified container within the Kubernetes service.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure that the Kubernetes credentials provided are valid and have sufficient permissions to access the specified namespace and service.
- Verify that the 'Resource Name' (service name) is correctly specified; missing or incorrect names will cause errors.
- Check that the 'Container Name' exists within the specified service; otherwise, logs cannot be retrieved.
- Common error: 'Resource name is required for logs operation!' indicates that the service name was not provided and must be set.