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, including ConfigMaps. Specifically, for the ConfigMap resource with the "Get" operation, it retrieves one or more ConfigMaps from a specified Kubernetes cluster environment.
Common scenarios where this node is beneficial include:
- Fetching configuration data stored in ConfigMaps to use in automation workflows.
- Auditing or monitoring ConfigMaps across different namespaces or projects.
- Integrating Kubernetes configuration data into other systems or processes.
For example, you might use this node to get all ConfigMaps in a particular namespace of a cluster to dynamically configure an application deployment pipeline.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster from which to retrieve the ConfigMap. Can be chosen from a list or specified by expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Can be chosen from a list or specified by expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project to scope the ConfigMap retrieval. Can be chosen from a list or specified by expression. |
These properties define the context (cluster, project, namespace) from which the ConfigMap(s) will be fetched.
Output
The output is a JSON object representing the retrieved ConfigMap(s). The structure corresponds to the Kubernetes ConfigMap resource schema, typically including metadata (like name, namespace, labels), data fields containing key-value pairs of configuration data, and possibly binary data encoded as strings.
If multiple ConfigMaps are retrieved, the output will be an array of such JSON objects.
No binary data output is indicated for this operation.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or API key credential configured in n8n to authenticate requests.
- The node depends on internal methods to load options for clusters, projects, and namespaces dynamically.
Troubleshooting
- Authentication errors: Ensure that the API credentials provided have sufficient permissions to read ConfigMaps in the specified cluster/project/namespace.
- Resource not found: If no ConfigMaps are returned, verify that the cluster, project, and namespace parameters are correct and that ConfigMaps exist there.
- Invalid parameter errors: Make sure required fields like Cluster Name or ID are set; optional fields can be left empty if not needed.
- API connectivity issues: Confirm network connectivity to the Rancher/Kubernetes API endpoint and that the endpoint URL is correctly configured in credentials.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Documentation
- n8n Expressions Documentation (for using expressions in property fields)