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 interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources. Specifically, for the ConfigMap resource with the Update operation, it updates an existing ConfigMap in a specified Kubernetes cluster environment.
Use cases include modifying configuration data stored in ConfigMaps without redeploying applications, enabling dynamic configuration changes in Kubernetes-managed applications. For example, you might update database connection strings or feature flags stored in a ConfigMap to change application behavior on the fly.
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 | (Optional) Select the project within the cluster. Choose from a list or specify an ID via expression. |
| Namespace Name or ID | (Optional) Select the namespace containing the ConfigMap. Choose from a list or specify an ID via expression. |
These properties are used to identify the exact location of the ConfigMap to update.
Additional properties relevant to updating a ConfigMap (inherited from the general node parameters but not explicitly listed here) would typically include the ConfigMap name and the new data or metadata to apply.
Output
The node outputs JSON data representing the updated ConfigMap resource as returned by the Rancher/Kubernetes API. This includes details such as the ConfigMap's metadata, data fields, and status after the update operation.
No binary data output is involved in this operation.
Dependencies
- Requires access 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 connectivity and permissions.
Troubleshooting
- Common issues:
- Incorrect cluster, project, or namespace selection leading to "resource not found" errors.
- Insufficient permissions to update ConfigMaps causing authorization failures.
- Network connectivity problems to the Rancher/Kubernetes API endpoint.
- Error messages:
- "Not Found" or "404" indicates the specified ConfigMap or namespace does not exist.
- "Unauthorized" or "403" suggests missing or invalid API credentials.
- Timeout or connection errors imply network or API availability issues.
- Resolutions:
- Verify cluster, project, and namespace IDs are correct and accessible.
- Ensure API credentials have sufficient permissions for ConfigMap updates.
- Check network connectivity and Rancher/Kubernetes API health.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property values)