Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Overview
This node interacts with Kubernetes clusters, specifically supporting operations on various Kubernetes resources including DaemonSets. For the 'exec' operation on DaemonSets, it allows executing commands inside the pods managed by the DaemonSet. This is useful for debugging, running maintenance commands, or inspecting the state of containers within the DaemonSet's pods. For example, a user can run shell commands inside a pod to check logs or configuration without needing direct cluster access.
Use Case Examples
- Executing a shell command inside a pod of a DaemonSet to troubleshoot an application issue.
- Running a maintenance script inside DaemonSet pods to update configurations or clear caches.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting pods, or when executing commands inside pods. |
| Namespace | The Kubernetes namespace where the DaemonSet resource is located. |
| Resource Name | The name of the DaemonSet resource on which the operation is performed. |
Output
JSON
stdout- The standard output from the executed command inside the pod.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the cluster.
Troubleshooting
- If no credentials are provided or credentials are invalid, the node throws an error 'No credentials got returned!'. Ensure valid Kubernetes API credentials are configured.
- The 'command' parameter must be a JSON array; otherwise, an error 'Command must be an array!' is thrown. Ensure the command is properly formatted as a JSON array of strings.