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, allowing users to perform various operations on Kubernetes resources such as ReplicaSets. Specifically, for the 'Patch' operation on ReplicaSets, it enables users to modify existing ReplicaSet resources within a specified namespace. This is useful for updating configurations or properties of ReplicaSets without recreating them. Practical examples include updating the image of containers in a ReplicaSet or changing resource limits dynamically.
Use Case Examples
- Patching a ReplicaSet to update the container image to a new version.
- Modifying the number of replicas in a ReplicaSet to scale the application.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, relevant for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the ReplicaSet resource resides. |
| Resource Name | The name of the specific ReplicaSet resource to patch. |
Output
JSON
stdout- The output or response from the Kubernetes API after performing the patch operation on the ReplicaSet.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure that Kubernetes credentials are correctly configured and accessible; otherwise, the node will throw a 'No credentials got returned!' error.
- The 'command' parameter must be a valid JSON array when used; otherwise, an error 'Command must be an array!' will be thrown.
- Verify that the specified namespace and resource name exist in the Kubernetes cluster to avoid resource not found errors.