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 Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically. Specifically, for the Secret resource with the Update operation, it allows users to update existing Kubernetes secrets within a specified cluster, project, and namespace.
Common scenarios where this node is beneficial include:
- Automating secret updates in CI/CD pipelines.
- Managing sensitive configuration data dynamically across environments.
- Synchronizing secrets from external vaults or services into Kubernetes clusters.
For example, you might use this node to update database credentials stored as a Kubernetes secret whenever they rotate, ensuring your applications always have access to the latest credentials without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the secret resides. You can choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. This depends on the selected cluster and can be chosen from a list or specified by ID. |
| Namespace Name or ID | Select the namespace within the project where the secret exists. Choose from a list or specify an ID using an expression. |
These properties are required to identify the exact location of the secret to update.
Output
The node outputs JSON data representing the result of the update operation on the secret resource. The output typically includes details about the updated secret object as returned by the Rancher/Kubernetes API.
If the node supports binary data output (not explicitly shown for the Secret update), it would represent any associated binary content of the secret, but this is not indicated in the provided code.
Dependencies
- Requires connection to a Rancher/Kubernetes API endpoint.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- 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 IDs: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- API authentication errors: Verify that the API key or token used has sufficient permissions to update secrets.
- Invalid secret data format: When updating secrets, ensure the payload conforms to Kubernetes secret specifications.
- Network connectivity issues: Confirm that n8n can reach the Rancher/Kubernetes API endpoint.
Common error messages may include authorization failures, resource not found, or validation errors from the Kubernetes API. Resolving these usually involves checking credentials, resource identifiers, and request payload correctness.
Links and References
- Kubernetes Secrets Documentation
- Rancher API Reference
- n8n Expressions Documentation (for specifying dynamic IDs)
This summary focuses on the "Secret" resource with the "Update" operation as requested, based on static analysis of the provided source code and property definitions.