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 Deployments. The 'Restart' operation allows users to restart a specified deployment within a given namespace. This is useful for scenarios where you need to refresh or redeploy an application without deleting it entirely. For example, restarting a deployment can help apply new configurations or recover from transient errors without downtime.
Use Case Examples
- Restart a deployment named 'my-deployment' in the 'default' namespace to refresh the application pods.
- Use the node to restart a deployment after updating environment variables or container images.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, relevant for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the deployment or resource is located. |
| Resource Name | The name of the specific Kubernetes resource (e.g., deployment) to operate on. |
Output
JSON
stdout- The standard output from the Kubernetes operation, such as logs or command output.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the cluster.
Troubleshooting
- If no credentials are returned, the node will throw an error indicating missing Kubernetes credentials. Ensure that valid credentials are configured.
- The 'command' parameter must be a JSON array when used; otherwise, an error is thrown. Verify the command format before execution.