Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node enables interaction with Rancher and Kubernetes APIs, specifically focusing on managing Kubernetes resources within a Rancher-managed cluster. For the ConfigMap resource with the Update operation, it allows users to update existing ConfigMaps in a specified namespace of a Kubernetes cluster.
Typical use cases include updating configuration data stored in ConfigMaps without redeploying applications, such as changing application settings, feature flags, or environment-specific parameters dynamically.
For example, you might update a ConfigMap to change database connection strings or toggle debug modes for an application running in Kubernetes.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the ConfigMap resides. Choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. Choose from a list or specify an ID via expression. |
| Namespace Name or ID | Select the namespace containing the ConfigMap. Depends on the selected project. Choose from a list or specify an ID via expression. |
These properties are required to identify the exact location of the ConfigMap to update.
Output
The node outputs JSON data representing the result of the update operation on the ConfigMap. This typically includes the updated ConfigMap's metadata and data fields as returned by the Rancher/Kubernetes API.
No binary data output is involved.
Dependencies
- Requires access to a Rancher-managed Kubernetes cluster.
- Needs an API authentication token or API key credential configured in n8n to authenticate requests to the Rancher/Kubernetes API.
- The node depends on methods to load options dynamically for clusters, projects, and namespaces.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection can cause failures in locating the ConfigMap.
- Insufficient permissions or invalid API credentials may lead to authorization errors.
- Providing incomplete or malformed update data could cause the API to reject the request.
Error messages:
- "Resource not found" — Verify that the cluster, project, namespace, and ConfigMap exist and are correctly specified.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
- "Invalid input" — Ensure the update payload conforms to expected schema and data types.
Resolving these usually involves verifying configuration inputs, ensuring proper API credentials, and validating the update data structure.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)