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 on Kubernetes resources. Specifically, for the ReplicaSets resource with the Restart operation, it allows restarting a ReplicaSet by leveraging Kubernetes API credentials. This is useful in scenarios where you need to refresh or restart ReplicaSets to apply new configurations or recover from issues without manually accessing the Kubernetes cluster. For example, restarting a ReplicaSet can help in rolling out updates or fixing stuck pods.
Use Case Examples
- Restarting a ReplicaSet in a specific namespace to apply new configurations.
- Automating the restart of ReplicaSets as part of a CI/CD pipeline to ensure the latest deployment is active.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting a pod related to the ReplicaSet. |
| Namespace | The Kubernetes namespace where the ReplicaSet resides. |
| Resource Name | The name of the ReplicaSet resource to operate on. |
Output
JSON
stdout- The standard output from running or restarting the pod, typically containing the result or status of the operation.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If no credentials are returned, the node will throw an error indicating missing Kubernetes credentials. Ensure that valid Kubernetes API credentials are configured.
- If the command parameter is not an array when running pods, an error will be thrown. Make sure the command input is a valid JSON array.