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 allows users to interact with Rancher and Kubernetes APIs to manage various Kubernetes resources, including workloads. Specifically, for the Workload resource with the Delete operation, the node deletes a specified workload within a Kubernetes cluster.
Common scenarios where this node is beneficial include:
- Automating cleanup of workloads that are no longer needed.
- Integrating workload deletion into CI/CD pipelines or operational workflows.
- Managing Kubernetes resources programmatically without direct kubectl usage.
For example, you can delete a workload by specifying the cluster, project, namespace, and workload identifier, enabling automated resource management in multi-cluster environments.
Properties
Name | Meaning |
---|---|
Cluster Name or ID | Select the Kubernetes cluster where the workload exists. 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. Can be chosen from a list or specified via an expression. |
These properties define the scope and location of the workload to delete.
Output
The node outputs JSON data representing the result of the delete operation on the workload. The exact structure depends on the Rancher/Kubernetes API response but typically includes status information 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 relies on dynamically loaded options for clusters, projects, and namespaces, which depend on proper API connectivity and permissions.
Troubleshooting
Common issues:
- Invalid or missing cluster/project/namespace identifiers leading to failed API calls.
- Insufficient permissions to delete workloads in the specified namespace.
- Network connectivity problems to the Rancher/Kubernetes API server.
Error messages:
- Authorization errors indicating invalid or missing API credentials. Solution: Verify and update the API authentication token.
- Resource not found errors if the specified workload does not exist. Solution: Confirm the workload identifier and namespace.
- Timeout or connection errors. Solution: Check network connectivity and API server availability.
Links and References
- Rancher API Documentation
- Kubernetes API Reference
- n8n Expressions Documentation (for using expressions in property fields)