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 allows users to interact with Rancher and Kubernetes APIs to manage various Kubernetes resources, including workloads. Specifically, the Workload - Update operation enables updating existing workload resources within a specified cluster, project, and namespace. This is useful for modifying configurations of running workloads such as deployments or stateful sets without recreating them.
Common scenarios include:
- Updating container images or environment variables in a workload.
- Changing the number of replicas or resource limits.
- Adjusting workload labels or annotations dynamically.
For example, you might update a workload to roll out a new version of an application by changing its container image or tweak environment variables to modify runtime behavior.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the target Kubernetes cluster by name or ID. You can choose from a list or specify an ID via expression. |
| Project Name or ID | (Optional) Select the project within the cluster. Choose from a list or specify an ID via expression. |
| Namespace Name or ID | (Optional) Select the namespace within the project. Choose from a list or specify an ID via expression. |
These properties define the scope where the workload exists and will be updated.
Output
The node outputs JSON data representing the result of the update operation on the workload. This typically includes details about the updated workload resource, such as its metadata, status, and spec fields reflecting the changes applied.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Rancher or Kubernetes API endpoint.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on dynamic loading methods to fetch clusters, projects, and namespaces for user selection.
Troubleshooting
- Missing or invalid cluster/project/namespace: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- API authentication errors: Verify that the API key or token has sufficient permissions to update workloads.
- Invalid workload parameters: Check that all required fields for the update are correctly set and valid according to Kubernetes API specifications.
- Network connectivity issues: Confirm network access to the Rancher/Kubernetes API server.
Error messages typically indicate permission issues, resource not found, or validation failures. Resolving these involves verifying credentials, resource identifiers, and input property correctness.