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 allowing users to perform various operations on Kubernetes resources. For the DaemonSets resource with the Get operation, the node retrieves detailed information about one or more DaemonSet objects within a specified namespace.
Common scenarios include:
- Fetching the current state and configuration of a specific DaemonSet by name.
- Listing DaemonSets filtered by labels or fields to monitor deployments across nodes.
- Integrating Kubernetes state checks into automated workflows for deployment validation or auditing.
Practical example:
- Retrieve details of a DaemonSet named
my-daemonsetin thedefaultnamespace to verify its pod template and update strategy before triggering an update workflow.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the DaemonSet resides. Defaults to "default". |
| Resource Name | The exact name of the DaemonSet resource to retrieve. If provided, the node fetches this specific DaemonSet; otherwise, it can list multiple DaemonSets based on selectors. |
| Field Selector | A field selector string to filter DaemonSets by specific object fields (e.g., metadata.name=my-daemonset). Useful for precise filtering according to Kubernetes field selector syntax. |
| Label Selector | A label selector string to filter DaemonSets by their labels (e.g., app=nginx). This helps select DaemonSets matching certain labels, following Kubernetes label selector syntax. |
Output
The node outputs JSON data representing the retrieved DaemonSet(s). The structure corresponds to the Kubernetes API response for DaemonSets, typically including metadata (name, namespace, labels), specification (pod template, update strategy), and status (current number of pods, ready pods, etc.).
If a specific DaemonSet name is provided, the output will be a single DaemonSet object. If no name is given, the output may be a list of DaemonSets matching the selectors.
No binary data output is produced by this operation.
Dependencies
- Requires valid Kubernetes cluster credentials configured in n8n, including access rights to query DaemonSets.
- The node depends on an internal Kubernetes client utility to communicate with the Kubernetes API.
- No additional external services are required beyond the Kubernetes API endpoint.
Troubleshooting
No credentials got returned!
This error indicates missing or misconfigured Kubernetes credentials in n8n. Ensure that the API authentication token or kubeconfig is correctly set up and accessible by the node.Empty or no results returned
Verify that the namespace, resource name, field selector, and label selector parameters are correct and that the user has permission to view DaemonSets in the specified namespace.Invalid field selector or label selector syntax
Incorrect selector strings can cause the API to return errors or empty results. Refer to Kubernetes documentation on field selectors and label selectors for proper syntax.