Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node allows users to interact with Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically within n8n workflows. Specifically, for the ConfigMap resource with the Delete operation, it enables deleting a ConfigMap from a specified Kubernetes namespace in a given cluster and project.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or temporary ConfigMaps in Kubernetes environments.
- Integrating Kubernetes ConfigMap management into CI/CD pipelines.
- Managing configuration data dynamically as part of infrastructure automation workflows.
For example, you can use this node to delete a ConfigMap after a deployment process completes or when a feature toggle stored in a ConfigMap is no longer needed.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the ConfigMap resides. You can choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. This depends on the selected cluster and can be chosen from a list or specified by ID. |
| Namespace Name or ID | Select the namespace containing the ConfigMap to delete. Choose from a list or specify an ID using an expression. |
These properties are required to identify the exact location of the ConfigMap to delete.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation details or status information returned by the Rancher/Kubernetes API about the deletion of the ConfigMap.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Rancher/Kubernetes API endpoint.
- Needs 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, and namespaces (
getClusters,getProjects,getNamespaces).
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection may cause the node to fail to locate the ConfigMap.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Attempting to delete a non-existent ConfigMap will result in an error from the Kubernetes API.
Error messages:
- "Resource not found" — Verify that the ConfigMap exists in the specified namespace.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
- "Invalid cluster/project/namespace" — Ensure the selected values are correct and accessible.
Resolving these typically involves verifying input parameters, ensuring proper API credentials, and confirming resource existence.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for specifying IDs dynamically)