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" resource with the "Create" operation enables creating new workloads within a specified cluster, project, and namespace. This is useful for automating deployment of applications or services in Kubernetes environments managed by Rancher.
Common scenarios include:
- Automating the creation of workloads as part of CI/CD pipelines.
- Managing Kubernetes workloads programmatically without manual intervention.
- Integrating Rancher workload management into broader automation workflows.
Example: Creating a new workload in a specific namespace of a Rancher-managed Kubernetes cluster by specifying the cluster, project, and namespace IDs.
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 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 will be created.
Output
The node outputs JSON data representing the result of the workload creation API call. The exact structure depends on the Rancher/Kubernetes API response but typically includes details about the created workload such as its metadata, status, and specifications.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication credential for Rancher/Kubernetes API access.
- The node depends on dynamic loading methods to populate options for clusters, projects, and namespaces.
- Proper configuration of Rancher API credentials in n8n is necessary.
Troubleshooting
- Missing or invalid cluster/project/namespace IDs: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- API authentication errors: Verify that the Rancher API credential is correctly configured and has sufficient permissions.
- Network connectivity issues: Confirm that n8n can reach the Rancher/Kubernetes API endpoint.
- Invalid input parameters: Double-check required fields and their formats, especially when using expressions.
Common error messages may relate to authorization failures, resource not found, or validation errors from the API. Resolving these usually involves checking credentials, resource identifiers, and network access.