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 such as Pods. For the 'Pods' resource and 'Restart' operation, it allows restarting a pod within a specified namespace. This is useful in scenarios where a pod needs to be refreshed or reset without deleting it manually. For example, restarting a pod to apply configuration changes or recover from an error state.
Use Case Examples
- Restarting a pod named 'my-pod' in the 'default' namespace to refresh its state.
- Automating pod restarts as part of a deployment pipeline to ensure updated containers are running.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting a pod. |
| Namespace | The Kubernetes namespace where the pod resides. |
| Resource Name | The name of the pod resource to operate on. |
Output
JSON
stdout- The standard output from the pod operation, such as logs or command output.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the 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' parameter must be a JSON array when running pods; otherwise, an error 'Command must be an array!' is thrown. Validate the command input format.
- Ensure the specified namespace and resource name exist in the Kubernetes cluster to avoid resource not found errors.