Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Namespaces → Exec
AI-generatedOverview
This node interacts with Kubernetes clusters, specifically supporting operations on various Kubernetes resources such as namespaces, pods, services, deployments, and more. The 'Exec' operation allows executing commands inside a pod within a specified namespace. This is useful for running scripts, debugging, or managing containerized applications directly from the workflow. For example, you can execute a shell command inside a pod to check logs or modify configurations dynamically.
Use Case Examples
- Executing a command inside a pod to retrieve application logs.
- Running a script inside a container to perform maintenance tasks.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or executing commands in a pod. |
| Namespace | The Kubernetes namespace where the target resource (e.g., pod) resides. |
| Resource Name | The name of the specific Kubernetes resource (e.g., pod) to target for the operation. |
Output
JSON
stdout- The standard output resulting from executing the command inside the pod.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If no credentials are provided or invalid, the node throws an error 'No credentials got returned!'. Ensure valid Kubernetes API credentials are configured.
- The 'command' input must be a JSON array; otherwise, an error 'Command must be an array!' is thrown. Validate the command format before execution.