Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Jobs → Exec
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on Kubernetes resources, specifically supporting the 'Exec' operation for executing commands inside a container of a Kubernetes Job. It is useful for running commands directly within a container for debugging, maintenance, or automation purposes. For example, you can execute shell commands inside a container of a Job to inspect its state or modify its environment without redeploying the container.
Use Case Examples
- Executing a shell command inside a container of a Kubernetes Job to check logs or environment variables.
- Running a diagnostic command inside a Job's container to troubleshoot issues.
Properties
| Name | Meaning |
|---|---|
| Image | The container image associated with the Job (used in some operations). |
| Namespace | The Kubernetes namespace where the Job is located. |
| Resource Name | The name of the specific Job resource to operate on. |
| Container Name | The name of the container inside the Job where the command will be executed. |
Output
JSON
stdout- The standard output from the executed command inside the container.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure Kubernetes credentials are correctly configured; missing or invalid credentials will cause errors.
- The 'Resource Name' parameter is mandatory for the exec operation; omitting it will result in an error.
- The 'command' parameter must be a valid JSON array; otherwise, the node will throw an error.
- If the specified container name does not exist in the Job, the exec command will fail.