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 allowing management of various Kubernetes resources such as namespaces, deployments, services, pods, statefulsets, configmaps, secrets, jobs, cronjobs, and nodes. For the Secret resource with the Create operation, it facilitates creating a new secret within a specified cluster, project, and namespace.
Common scenarios include automating Kubernetes secret creation for storing sensitive data like API keys, passwords, or certificates securely within your Kubernetes environment. This is useful in CI/CD pipelines, automated infrastructure provisioning, or dynamic secret management workflows.
Example use case: Automatically create a Kubernetes secret containing database credentials when deploying an application, ensuring the app can access the credentials securely without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the target Kubernetes cluster by name or ID where the secret will be created. |
| Project Name or ID | Select the project within the chosen cluster to scope the secret creation. |
| Namespace Name or ID | Select the namespace within the project where the secret will be created. |
These properties are required and support selecting from dynamically loaded options or specifying IDs via expressions.
Output
The node outputs an array of JSON objects representing the response from the Rancher/Kubernetes API after creating the secret. Each output item contains a json field with the details of the created secret resource, including metadata and status as returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Rancher/Kubernetes API endpoint.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on dynamic loading methods to fetch available clusters, projects, and namespaces for selection.
Troubleshooting
- Missing or invalid cluster/project/namespace: Ensure that the selected cluster, project, and namespace exist and that the API credentials have sufficient permissions to access them.
- API authentication errors: Verify that the API key or token credential is correctly configured and has the necessary scopes.
- Resource creation failures: Check the error message returned by the API for issues such as duplicate secret names, invalid secret data format, or insufficient permissions.
- Dynamic option loading fails: Confirm network connectivity and API availability for loading clusters, projects, and namespaces.
Links and References
- Kubernetes Secrets Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)