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, specifically managing various Kubernetes resources. For the ConfigMap resource with the Delete operation, it deletes a specified ConfigMap from a Kubernetes cluster. This is useful for cleaning up configuration data that is no longer needed or to automate environment resets.
Typical use cases include:
- Removing obsolete or temporary ConfigMaps during CI/CD pipelines.
- Automating cleanup tasks in Kubernetes environments.
- Managing configuration lifecycle programmatically within workflows.
Example: Automatically delete a ConfigMap after a deployment completes to ensure no stale configuration remains.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the ConfigMap exists. Can be chosen from a list or specified via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Can be chosen from a list or specified via expression. |
| Namespace Name or ID | (Optional) Select the namespace containing the ConfigMap. Can be chosen from a list or specified via expression. |
These properties identify the exact location of the ConfigMap to delete.
Output
The node outputs an array of JSON objects representing the result of the delete operation for each input item processed. The json output field contains the response from the Rancher/Kubernetes API confirming deletion or providing error details.
No binary data is output by this node.
Dependencies
- Requires connection to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on dynamically loaded options for clusters, projects, and namespaces, which require proper API access permissions.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace identifiers leading to "resource not found" errors.
- Insufficient permissions or invalid API credentials causing authorization failures.
- Attempting to delete a ConfigMap that does not exist results in an error from the API.
Error messages:
- "Not Found" — Verify the cluster, project, namespace, and ConfigMap name are correct.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
- "Conflict" or "Resource in use" — Ensure the ConfigMap is not locked or referenced by other resources.
Resolving these typically involves verifying input parameters, ensuring correct API credentials, and checking resource dependencies.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)