Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
ReplicaSets → Exec
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on resources such as ReplicaSets. Specifically, the 'Exec' operation allows executing a command inside a container of a ReplicaSet pod. This is useful for debugging, running scripts, or managing containers directly within the Kubernetes environment. For example, you can run shell commands inside a container to inspect its state or troubleshoot issues.
Use Case Examples
- Executing a shell command inside a container of a ReplicaSet pod to check logs or configuration files.
- Running a diagnostic command inside a container to gather runtime information.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, relevant for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the ReplicaSet resides. |
| Resource Name | The name of the ReplicaSet resource to target. |
| Container Name | The name of the container inside the ReplicaSet pod 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 credentials will cause the node to throw an error.
- 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 indicating the command must be an array.