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 enables interaction with Rancher and Kubernetes APIs, specifically allowing users to manage Kubernetes resources programmatically within n8n workflows. For the ConfigMap Create operation, it facilitates creating a new ConfigMap resource in a specified Kubernetes cluster, project, and namespace.
Use cases include:
- Automating configuration management by dynamically creating ConfigMaps during deployment pipelines.
- Managing environment-specific configurations without manual intervention.
- Integrating Kubernetes ConfigMap creation into broader automation workflows, such as CI/CD or infrastructure provisioning.
Example: Automatically create a ConfigMap containing application settings before deploying an app, ensuring the app has the latest configuration data.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the ConfigMap resource to create. |
| Cluster Name or ID | Select the Kubernetes cluster where the ConfigMap will be created. Can choose from a list or use an expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Can choose from a list or use an expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project where the ConfigMap will be created. Can choose from a list or use an expression. |
| Labels | Optional key-value pairs to label the ConfigMap for identification or grouping purposes. |
| Annotations | Optional key-value pairs to annotate the ConfigMap with metadata. |
Output
The node outputs JSON data representing the created ConfigMap resource as returned by the Rancher/Kubernetes API. This typically includes details such as the ConfigMap's metadata (name, labels, annotations), data content, and status information.
If the node supports binary data output (not indicated here), it would represent any associated binary payloads related to the resource.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The node depends on dynamic loading of clusters, projects, and namespaces via internal methods to populate dropdown options.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection can cause failures.
- Insufficient permissions on the Kubernetes cluster may result in authorization errors.
- Providing invalid names or labels might lead to API validation errors.
Error messages:
- Authorization errors indicate missing or invalid API credentials; verify and update credentials.
- Resource not found errors suggest incorrect cluster/project/namespace IDs; double-check selections.
- Validation errors on input fields require correcting property values according to Kubernetes naming conventions.
Links and References
- Kubernetes ConfigMap Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)