Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node integrates with the Rancher/Kubernetes API to manage various Kubernetes resources, including ConfigMaps. Specifically, for the ConfigMap - Get operation, it retrieves one or more ConfigMaps from a specified Kubernetes namespace within a project and cluster.
Use cases include:
- Fetching configuration data stored in ConfigMaps to use in workflows.
- Auditing or monitoring ConfigMap contents.
- Dynamically retrieving environment configurations for applications running in Kubernetes.
For example, you might use this node to get the current ConfigMap settings before updating them or to read configuration values that influence subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster by name or ID. You can choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster by name or ID. Depends on the selected cluster. |
| Namespace Name or ID | Select the namespace within the project by name or ID. Depends on the selected project. |
These properties are required to scope the ConfigMap retrieval to the correct Kubernetes context.
Output
The node outputs an array of JSON objects representing the retrieved ConfigMap(s). Each item contains the full details of a ConfigMap resource as returned by the Rancher/Kubernetes API, including metadata (like name, labels, annotations), data entries (key-value pairs stored in the ConfigMap), and other relevant fields.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Rancher or Kubernetes cluster API.
- Needs an API authentication credential configured in n8n to authorize requests to the Rancher/Kubernetes API.
- The node depends on dynamic loading methods to populate options for clusters, projects, and namespaces (
getClusters,getProjects,getNamespaces).
Troubleshooting
- Missing or incorrect cluster/project/namespace selection: Ensure that the selected cluster, project, and namespace exist and that your API credentials have permission to access them.
- API authentication errors: Verify that the API key or token used has sufficient permissions and is correctly configured in n8n.
- Empty results: If no ConfigMaps are returned, confirm that ConfigMaps exist in the specified namespace.
- Network or connectivity issues: Check network access to the Rancher/Kubernetes API endpoint.
Common error messages typically relate to authorization failures, resource not found, or invalid parameters. Resolving these usually involves verifying credentials, resource names/IDs, and network connectivity.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)