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. For the Secret resource with the Delete operation, it deletes a specified secret within a Kubernetes namespace.
Typical use cases include automating cleanup of secrets that are no longer needed or managing secrets lifecycle as part of CI/CD pipelines or infrastructure automation workflows.
For example, you might use this node to delete a secret after a deployment is complete or when rotating credentials stored as Kubernetes secrets.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the secret exists. You can choose from a list or specify an ID via expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. |
| Namespace Name or ID | Select the namespace within the project where the secret resides. |
These properties are required to precisely identify the location of the secret to be deleted.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will contain confirmation details or status information returned by the Rancher/Kubernetes API about the deletion.
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 for Rancher/Kubernetes access.
- The node depends on dynamic loading of clusters, projects, and namespaces via internal methods to populate options.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace selection may cause the node to fail to locate the secret.
- Insufficient permissions in the Kubernetes cluster to delete secrets will result in authorization errors.
- Network connectivity issues to the Rancher/Kubernetes API endpoint can cause timeouts or failures.
Error messages:
- Authorization errors typically indicate missing or invalid API credentials or insufficient RBAC permissions.
- Resource not found errors suggest the secret does not exist in the specified namespace.
- Validation errors may occur if required parameters are missing or malformed.
To resolve these:
- Verify API credentials and permissions.
- Confirm the secret exists in the specified namespace.
- Check network connectivity and Rancher/Kubernetes API availability.
Links and References
- Kubernetes Secrets Documentation
- Rancher API Reference
- n8n Expressions Documentation (for specifying IDs dynamically)