Actions90
- Jobs Actions
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- CronJobs Actions
Overview
This node allows interaction with Kubernetes resources, specifically supporting operations such as deleting a DaemonSet. In the context of the "Delete" operation for the "DaemonSets" resource, the node deletes a specified DaemonSet within a given namespace.
Common scenarios where this node is beneficial include automating Kubernetes cluster management tasks, such as cleaning up or removing outdated or unnecessary DaemonSets programmatically as part of CI/CD pipelines or infrastructure automation workflows.
For example, you might use this node to delete a DaemonSet that deploys a logging agent on all nodes when you want to replace it with a new version or remove it entirely.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the DaemonSet exists. Defaults to "default". |
| Resource Name | The name of the DaemonSet resource to delete. |
Output
The node outputs JSON data representing the result of the delete operation. This typically includes status information returned by the Kubernetes API about the deletion request, such as confirmation of deletion or error details if the resource was not found or could not be deleted.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Kubernetes API.
- The node depends on a Kubernetes client utility internally to perform API calls.
- Proper permissions are needed in the Kubernetes cluster to delete DaemonSets in the specified namespace.
Troubleshooting
No credentials got returned!
This error indicates missing or misconfigured Kubernetes API credentials. Ensure that valid credentials are provided and correctly referenced in the node configuration.Resource not found or permission denied errors
These occur if the specified DaemonSet name does not exist in the given namespace or if the credentials lack sufficient permissions. Verify the resource name, namespace, and RBAC permissions.Invalid input errors
If required properties like "Resource Name" or "Namespace" are empty or invalid, the node may fail. Double-check input values before execution.