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. Specifically, for the Secret resource with the Delete operation, it enables users to delete a secret from a specified cluster, project, and namespace within a Kubernetes environment managed by Rancher.
Common scenarios where this node is beneficial include:
- Automating cleanup of sensitive data stored as secrets in Kubernetes.
- Managing lifecycle of secrets programmatically as part of CI/CD pipelines.
- Removing outdated or compromised secrets securely without manual intervention.
Example use case:
- A DevOps engineer wants to delete a Kubernetes secret named "db-credentials" from a specific namespace after rotating credentials. This node can be configured to target the correct cluster, project, and namespace, then delete the secret automatically.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the secret exists. Can choose from a list or specify an ID via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Can choose from a list or specify an ID via expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project. Can choose from a list or specify an ID via expression. |
These properties define the scope and location of the secret to be deleted.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation details or status information returned by the Rancher/Kubernetes API about the deletion of the secret.
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 credential configured in n8n to authorize requests.
- The node depends on dynamic loading methods to fetch available clusters, projects, and namespaces for user selection.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace identifiers may cause the deletion to fail.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Trying to delete a non-existent secret will result in an error from the API.
Error messages and resolutions:
- "Unauthorized" or "Forbidden": Check that the API key or token has sufficient permissions to delete secrets.
- "Not Found": Verify that the secret exists in the specified namespace and project.
- "Invalid cluster/project/namespace": Ensure the selected IDs are correct and accessible.
Links and References
- Kubernetes Secrets Documentation
- Rancher API Reference
- n8n Expressions Documentation (for using expressions in property fields)