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 such as running pods, deleting resources, executing commands, and patching resources. Specifically, for the 'Patch' operation on the 'CronJobs' resource, it enables updating or modifying existing CronJob resources within a specified namespace. This node is beneficial for automating Kubernetes management tasks, such as updating configurations or scaling jobs without manual intervention.
Use Case Examples
- Patching a CronJob to update its schedule or job template in a Kubernetes cluster.
- Automating the update of Kubernetes resources as part of a CI/CD pipeline.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, relevant for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the resource (e.g., CronJob) is located. |
| Resource Name | The name of the specific Kubernetes resource (e.g., CronJob) to operate on. |
Output
JSON
stdout- Output from running a pod or executing a command in Kubernetes.
Dependencies
- Requires Kubernetes API credentials for authentication and interaction with the Kubernetes cluster.
Troubleshooting
- Error 'No credentials got returned!' indicates missing or invalid Kubernetes API credentials; ensure credentials are properly configured.
- Error 'Command must be an array!' occurs if the command input is not a valid JSON array; verify the command format.