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, specifically supporting operations on various Kubernetes resources including Jobs. The 'Patch' operation allows users to modify existing Kubernetes resources by applying partial updates. This is useful for dynamically updating configurations or states of Kubernetes Jobs without needing to recreate them. For example, a user can patch a Job to change its parallelism or update labels.
Use Case Examples
- Patching a Kubernetes Job to update its metadata or spec fields.
- Modifying a Job's configuration in a specific namespace to adjust its behavior.
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 (Job) resides. Defaults to 'default' if not specified. |
| Resource Name | The name of the specific Kubernetes resource (Job) to operate on. |
Output
JSON
stdout- The standard output from running a pod or executing a command in Kubernetes.
Dependencies
- Requires Kubernetes API credentials for authentication and interaction with the cluster.
Troubleshooting
- Ensure Kubernetes credentials are correctly configured and accessible; missing credentials will cause the node to 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.