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 "Pause Deployment" operation in this Rancher node allows users to pause a specific deployment within a Kubernetes cluster managed by Rancher. Pausing a deployment typically suspends its rollout or update process, which can be useful for temporarily halting changes to the deployment without deleting or scaling it down.
Common scenarios where this node is beneficial include:
- Temporarily stopping an ongoing deployment rollout to investigate issues.
- Pausing automated updates during maintenance windows.
- Controlling deployment states programmatically as part of CI/CD pipelines.
For example, you might use this node to pause a deployment named "web-app" in a particular namespace and project on a selected cluster before applying manual configuration changes.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster where the deployment resides. 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. |
| Deployment ID | The unique identifier of the deployment to pause. Must be selected from a list filtered by project and namespace. |
Output
The node outputs JSON data representing the result of the pause operation on the specified deployment. This typically includes details about the deployment's updated state after being paused, such as metadata and status fields returned by the Rancher/Kubernetes API.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Rancher-managed Kubernetes cluster.
- Needs an API authentication credential configured in n8n to connect securely to the Rancher API.
- The node depends on dynamic loading methods to fetch available clusters, projects, namespaces, and deployments for selection.
Troubleshooting
Common Issues:
- Incorrect or missing cluster/project/namespace/deployment identifiers may cause failures.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Network connectivity problems with the Rancher server will prevent API calls.
Error Messages:
- "Deployment not found": Verify that the deployment ID is correct and exists in the specified namespace/project.
- "Unauthorized" or "Forbidden": Check that the API key has sufficient permissions.
- Timeout or connection errors: Ensure network access to the Rancher API endpoint.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network connectivity.
Links and References
- Rancher Official Documentation
- Kubernetes Deployments
- n8n Expressions Documentation (for using expressions in property fields)