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 to perform various operations such as running pods, deleting resources, executing commands, restarting resources, and more. Specifically, for the 'Namespaces' resource with the 'Restart' operation, it allows restarting a namespace or related resource within a Kubernetes cluster. This is useful for managing Kubernetes environments programmatically, for example, restarting a namespace to refresh its state or apply new configurations.
Use Case Examples
- Restarting a Kubernetes namespace to refresh its state after configuration changes.
- Automating the restart of namespaces as part of a deployment pipeline to ensure clean environments.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting pods or executing commands within the Kubernetes cluster. |
| Namespace | The Kubernetes namespace in which the operation (such as restart) will be performed. |
| Resource Name | The name of the specific Kubernetes resource (e.g., pod, deployment) to target for the operation. |
Output
JSON
stdout- The standard output from running a pod or executing a command in the Kubernetes cluster.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If no credentials are returned, the node throws an error 'No credentials got returned!'. Ensure that valid Kubernetes API credentials are configured and accessible.
- If the 'command' parameter is not an array when running a pod, an error 'Command must be an array!' is thrown. Ensure the command is provided as a JSON array.