Actions54
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
- Node Actions
- Workload Actions
Overview
This node enables interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources, including StatefulSets. Specifically, for the StatefulSet Delete operation, it allows users to delete a specified StatefulSet resource within a Kubernetes cluster.
Common scenarios where this node is beneficial include:
- Automating cleanup of StatefulSets that are no longer needed.
- Managing lifecycle of stateful applications by programmatically removing their StatefulSets.
- Integrating Kubernetes resource management into broader workflows, such as CI/CD pipelines or infrastructure automation.
For example, you might use this node to delete a StatefulSet representing a database cluster after backing up data, or to remove test environments dynamically created during automated testing.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the StatefulSet resides. Can be chosen from a list or specified via an expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Can be chosen from a list or specified via an expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project where the StatefulSet exists. Can be chosen from a list or specified via an expression. |
| StatefulSet ID | The identifier of the StatefulSet to delete. Must be selected from a list filtered by the chosen project and namespace. |
Output
The node outputs JSON data representing the result of the delete operation on the StatefulSet. This typically includes confirmation details or status information returned by the Rancher/Kubernetes API about the deletion request.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Requires an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on dynamic loading methods to populate options for clusters, projects, namespaces, and StatefulSets, which require proper API connectivity.
Troubleshooting
Common issues:
- Invalid or missing cluster/project/namespace selection can cause failures in locating the StatefulSet.
- Insufficient permissions or invalid API credentials may lead to authorization errors.
- Attempting to delete a non-existent StatefulSet will result in an error from the API.
Error messages and resolutions:
- "Not Found" — Verify that the StatefulSet ID, namespace, project, and cluster are correct.
- "Unauthorized" or "Forbidden" — Check API credentials and ensure the user has permission to delete StatefulSets.
- Timeouts or connection errors — Confirm network connectivity to the Rancher/Kubernetes API endpoint.