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, supporting various operations on Kubernetes resources such as StatefulSets. Specifically, the 'Restart' operation allows restarting a StatefulSet by running a pod with a specified image and command in a given namespace. This is useful for scenarios where you need to refresh or restart StatefulSets without manually accessing the Kubernetes cluster. For example, you can automate restarting a StatefulSet after updating its configuration or image.
Use Case Examples
- Restart a StatefulSet in the 'default' namespace using a specific container image to apply updates or refresh the service.
- Run a custom command in a pod within a StatefulSet to troubleshoot or perform maintenance tasks.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting a pod associated with the StatefulSet. |
| Namespace | The Kubernetes namespace where the StatefulSet resource is located. |
| Resource Name | The name of the StatefulSet resource to operate on. |
Output
JSON
stdout- The standard output from running the pod or command associated with the StatefulSet operation.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If no credentials are provided or returned, the node throws an error 'No credentials got returned!'. Ensure Kubernetes API credentials are correctly configured.
- If the 'command' parameter is not an array when running a pod, an error 'Command must be an array!' is thrown. Provide the command as a JSON array.