Actions90
- Jobs Actions
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- CronJobs Actions
Overview
This node enables interaction with Kubernetes clusters, specifically supporting various operations on Kubernetes resources such as DaemonSets. For the List operation on DaemonSets, it retrieves a list of DaemonSet resources from a specified namespace in the cluster. This is useful for monitoring, auditing, or automating workflows that depend on the current state of DaemonSets.
Common scenarios include:
- Fetching all DaemonSets in a namespace to check their status or configuration.
- Filtering DaemonSets by labels or fields to narrow down results.
- Integrating Kubernetes resource data into automation pipelines or dashboards.
Example: List all DaemonSets in the "default" namespace that match a specific label selector to monitor deployments related to a particular application.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace from which to list DaemonSets. Defaults to "default". |
| Resource Name | (Optional) Specific name of a DaemonSet resource to retrieve. If provided, the list will be filtered to this resource name. |
| Field Selector | (Optional) A field selector string to filter DaemonSets based on resource fields. See Kubernetes Field Selectors for syntax and usage. |
| Label Selector | (Optional) A label selector string to filter DaemonSets based on labels. See Kubernetes Labels for syntax and usage. |
Output
The output is a JSON array where each item represents a DaemonSet resource matching the query parameters. Each item contains the full Kubernetes API representation of the DaemonSet, including metadata, spec, and status fields.
The structure corresponds directly to the Kubernetes API response for DaemonSets, enabling downstream nodes or workflows to access detailed information about each DaemonSet.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kubernetes cluster accessible via configured credentials.
- The node depends on a valid API authentication token or key credential to connect to the Kubernetes API server.
- Proper RBAC permissions are needed to list DaemonSets in the target namespace.
- No additional external services beyond Kubernetes API are required.
Troubleshooting
No credentials got returned!
This error indicates missing or misconfigured Kubernetes API credentials. Ensure that the node has been provided with valid credentials that allow API access.Command must be an array!
Although not relevant for the List operation, this error may appear if the node is used with the Run operation and the command input is incorrectly formatted. Commands must be provided as a JSON array.Permission Denied or Forbidden Errors
These occur if the API token lacks permission to list DaemonSets in the specified namespace. Verify RBAC settings and ensure the token has sufficient privileges.Empty Results
If no DaemonSets are returned, verify the namespace, label selectors, and field selectors for correctness. Also confirm that DaemonSets exist in the targeted namespace.