Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
CronJobs → Patch
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on Kubernetes resources, specifically supporting the 'Patch' operation for CronJobs in this context. It allows users to modify existing Kubernetes resources by applying patch data, which is useful for updating configurations or properties of CronJobs without recreating them. Practical examples include updating the schedule or job template of a CronJob dynamically within an automation workflow.
Use Case Examples
- Updating the schedule of a Kubernetes CronJob by patching its spec.schedule field.
- Modifying the container image or environment variables of a CronJob using patch data.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, applicable for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the CronJob resource resides. |
| Resource Name | The name of the specific CronJob resource to patch. |
| Patch Data | The JSON object containing the patch data to apply to the CronJob resource. |
Output
JSON
json- The JSON response from the Kubernetes API after applying the patch to the CronJob resource.
Dependencies
- Requires Kubernetes API credentials for authentication and interaction 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.
- Patch data must be a valid JSON object; invalid JSON will cause errors.
- Kubernetes credentials must be correctly configured and valid to avoid authentication errors.
Links
- Kubernetes Patch Documentation - Official Kubernetes documentation on how to patch resources.