Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
ReplicaSets → Logs
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on resources such as ReplicaSets. Specifically, for the Logs operation on ReplicaSets, it retrieves the logs of a specified container within a ReplicaSet in a given namespace. This is useful for monitoring and debugging applications running in Kubernetes clusters by accessing their runtime logs.
Use Case Examples
- Retrieve logs from the main container of a ReplicaSet named 'my-replicaset' in the 'default' namespace to diagnose issues or monitor application behavior.
- Fetch logs from a specific container within a ReplicaSet to analyze application output or errors.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the ReplicaSet is located. |
| Resource Name | The name of the ReplicaSet resource to retrieve logs from. |
| Container Name | The name of the container within the ReplicaSet to get logs from. |
Output
JSON
logs- The logs output from the specified container within the ReplicaSet.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If the 'Resource Name' is not provided, the node throws an error indicating that the resource name is required for the logs operation.
- Ensure the Kubernetes credentials are correctly configured; otherwise, the node will throw an error stating no credentials were returned.
- If the specified container name does not exist in the ReplicaSet, the logs retrieval may fail or return empty logs.