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 interacts with Rancher and Kubernetes APIs to manage various Kubernetes resources. Specifically, the Deployment Rollback operation allows users to revert a deployment to a previous revision. This is useful in scenarios where a recent deployment introduced issues or bugs, and you want to quickly restore the application to a known stable state.
Practical examples include:
- Rolling back a web application deployment after a failed update.
- Reverting a microservice to a previous version when new features cause errors.
- Quickly restoring service availability by undoing problematic changes.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster to operate on. Can be chosen from a list or specified via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Depends on the selected cluster. |
| Namespace Name or ID | (Optional) Select the namespace within the project. Depends on the selected project. |
| Deployment ID | The identifier of the deployment to rollback. Must be selected or specified. |
| Revision ID | The identifier of the revision to rollback to. This specifies which previous deployment version to restore. |
Output
The node outputs JSON data representing the result of the rollback operation. This typically includes details about the deployment status after rollback, such as metadata, current revision, and any relevant API response information confirming the rollback success.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or key configured in n8n credentials for Rancher/Kubernetes API access.
- The node depends on dynamic loading methods to fetch clusters, projects, namespaces, and deployments for user selection.
Troubleshooting
Common Issues:
- Invalid or missing cluster/project/namespace/deployment IDs can cause failures.
- Insufficient permissions on the Kubernetes cluster to perform rollbacks.
- Incorrect revision ID that does not exist for the deployment.
Error Messages:
- "Deployment not found" — Verify the deployment ID and namespace are correct.
- "Revision ID invalid" — Ensure the revision ID corresponds to an existing deployment revision.
- "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
Resolutions:
- Double-check all input parameters, especially IDs.
- Confirm the API credentials have sufficient rights.
- Use the Rancher/Kubernetes dashboard or CLI to verify available revisions.
Links and References
- Kubernetes Rollback Documentation
- Rancher API Documentation
- n8n Expressions Documentation (for using expressions in property fields)