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 DaemonSets. Specifically, for the 'Patch' operation on DaemonSets, it enables users to modify existing DaemonSet resources within a specified namespace. This is useful for updating configurations or applying changes to running DaemonSets without recreating them. Practical examples include updating container images or adjusting resource limits in a DaemonSet.
Use Case Examples
- Patching a DaemonSet to update the container image to a new version.
- Modifying the resource limits of containers in a DaemonSet to optimize performance.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use, relevant for operations like run, restart, exec, and patch. |
| Namespace | The Kubernetes namespace where the DaemonSet resource resides. |
| Resource Name | The name of the DaemonSet resource to be patched. |
Output
JSON
stdout- Output from running a pod command or operation result.
Dependencies
- Requires Kubernetes API credentials for authentication and interaction with the Kubernetes cluster.
Troubleshooting
- Ensure Kubernetes credentials are correctly configured; 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.