Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Namespaces → Logs
AI-generatedOverview
This node interacts with Kubernetes clusters to perform various operations on Kubernetes resources. Specifically for the 'Namespaces' resource with the 'Logs' operation, it retrieves logs from a specified container within a pod in a given namespace. This is useful for monitoring and debugging applications running in Kubernetes by accessing their runtime logs.
Use Case Examples
- Fetching logs from a specific container in a pod within a namespace to troubleshoot application issues.
- Monitoring real-time logs of a container to analyze application behavior during deployment or testing.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the target resource (pod) resides. |
| Resource Name | The name of the specific resource (pod) from which to retrieve logs. |
| Container Name | The name of the container within the pod to fetch logs from. Defaults to 'main-container'. |
Output
JSON
logs- The logs output from the specified container in the pod.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Error 'Resource name is required for logs operation!' indicates that the resource name (pod name) was not provided; ensure this parameter is set.
- If logs are empty or missing, verify the container name is correct and the pod is running.
- Authentication errors suggest issues with Kubernetes credentials; verify the API key or token is valid and has necessary permissions.
Links
- Kubernetes Namespaces - Official documentation on Kubernetes namespaces and their usage.
- Kubernetes Logging Architecture - Details on how logging works in Kubernetes and how to access container logs.