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 to manage various Kubernetes resources, including workloads. Specifically for the Workload resource with the Pause operation, it allows users to pause a workload within a specified cluster, project, and namespace context.
Pausing a workload typically means suspending its activity or scaling it down temporarily without deleting it. This can be useful in scenarios such as:
- Temporarily halting processing during maintenance windows.
- Pausing workloads to save resources when not needed.
- Controlling deployment rollouts by pausing ongoing updates.
For example, a user might pause a workload before applying configuration changes or upgrades, then resume it afterward.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the target cluster by name or ID. You can choose from a list or specify an ID using an expression. |
| Project Name or ID | (Optional) Select the project within the cluster by name or ID. Depends on the selected cluster. |
| Namespace Name or ID | (Optional) Select the namespace within the project by name or ID. Depends on the selected project. |
These properties define the scope where the workload exists and where the pause operation will be applied.
Output
The node outputs JSON data representing the result of the pause operation on the workload. The exact structure depends on the Rancher/Kubernetes API response but generally includes details about the workload's updated state after being paused.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Rancher or Kubernetes API endpoint.
- Needs an API authentication credential configured in n8n to authorize requests.
- Uses dynamic loading methods to populate options for clusters, projects, and namespaces.
Troubleshooting
- Missing or invalid cluster/project/namespace: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- Permission errors: The API key or token used must have sufficient permissions to pause workloads in the specified namespace.
- Invalid workload state: Attempting to pause a workload that is already paused or in an incompatible state may cause errors.
- Network or API connectivity issues: Verify network access to the Rancher/Kubernetes API and correct API endpoint configuration.
Common error messages will relate to authorization failures, resource not found, or invalid parameters. Resolving these usually involves checking credentials, resource identifiers, and API access rights.
Links and References
- Rancher API Documentation
- Kubernetes Workloads Concepts
- n8n Expressions Documentation (for specifying IDs dynamically)