Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
ReplicaSets → Patch
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on resources, specifically here focusing on the 'Patch' operation for ReplicaSets. It allows users to modify existing ReplicaSet resources in a Kubernetes cluster by applying JSON patch data. This is useful for updating configurations or properties of ReplicaSets without recreating them, such as changing labels, annotations, or other spec fields.
Use Case Examples
- Updating the number of replicas in a ReplicaSet by patching the 'spec.replicas' field.
- Modifying labels or annotations on a ReplicaSet to change its metadata.
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 ReplicaSet resource to patch. |
| Patch Data | The JSON patch data to apply to the ReplicaSet resource, specifying the changes to be made. |
Output
JSON
json- The JSON response from the Kubernetes API after applying the patch to the ReplicaSet resource.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure that the 'Resource Name' is provided; otherwise, the node will throw an error indicating the resource name is required for the patch operation.
- The 'Patch Data' must be valid JSON; invalid JSON will cause errors when parsing or applying the patch.
- Kubernetes API credentials must be correctly configured and valid to avoid authentication errors.
- If the specified ReplicaSet does not exist or the user lacks permissions, the patch operation will fail with an error from the Kubernetes API.