Actions54
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
- Node Actions
- Workload Actions
Overview
The node provides integration with Rancher and Kubernetes APIs, allowing users to manage various Kubernetes resources programmatically within n8n workflows. Specifically, the "Deployment" resource with the "Resume" operation enables resuming a paused deployment in a Kubernetes cluster managed by Rancher.
This is useful in scenarios where deployments have been paused (e.g., for maintenance or updates) and need to be resumed to continue rolling out changes or scaling operations. For example, after pausing a deployment to apply configuration changes safely, you can use this node to resume it automatically as part of your CI/CD pipeline.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the target Kubernetes cluster by name or ID. |
| Project Name or ID | (Optional) Select the project within the cluster. |
| Namespace Name or ID | (Optional) Select the namespace within the project. |
| Deployment ID | The identifier of the deployment to resume. |
These properties allow precise targeting of the deployment resource within the Rancher-managed Kubernetes environment.
Output
The node outputs JSON data representing the result of the resume operation on the specified deployment. This typically includes the updated deployment status and metadata confirming that the deployment has been resumed successfully.
No binary data output is involved.
Dependencies
- Requires an API authentication credential for Rancher/Kubernetes.
- Needs access to the Rancher API endpoint managing the Kubernetes clusters.
- The node depends on internal methods to load options dynamically for clusters, projects, namespaces, and deployments.
Troubleshooting
Common issues:
- Incorrect or missing cluster/project/namespace/deployment identifiers may cause failures.
- Insufficient permissions or invalid API credentials will prevent successful API calls.
- Attempting to resume a deployment that is not paused might result in no changes or errors.
Error messages:
- Authentication errors indicate problems with the provided API key or token; verify credentials.
- Resource not found errors suggest incorrect IDs or that the deployment does not exist in the specified scope.
- Permission denied errors mean the API user lacks rights to modify the deployment; check RBAC settings.
Resolving these usually involves verifying input parameters, ensuring correct API credentials, and confirming user permissions in Rancher/Kubernetes.
Links and References
- Rancher API Documentation
- Kubernetes Deployments
- n8n Expressions (for dynamic property values)