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 interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically within n8n workflows. It supports operations on multiple resource types such as namespaces, deployments, services, pods, statefulsets, configmaps, nodes, workloads, and more.
For the Node resource with the Get operation, the node fetches information about one or more Kubernetes nodes in a specified cluster, optionally filtered by project and namespace context.
Common scenarios include:
- Retrieving details of nodes in a Kubernetes cluster for monitoring or auditing.
- Integrating node status checks into automated workflows.
- Using node metadata to trigger conditional logic in infrastructure automation.
Example: Automatically fetching all nodes in a cluster to verify their readiness before deploying new workloads.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster from which to retrieve node information. |
| Project Name or ID | (Optional) Specify the project within the cluster to scope the node query. |
| Namespace Name or ID | (Optional) Specify the namespace within the project to further scope the node query. |
These properties allow users to specify the exact cluster and optionally narrow down the scope by project and namespace when retrieving node data.
Output
The output is an array of JSON objects representing the nodes retrieved from the Kubernetes cluster. Each object contains detailed information about a node, such as its metadata, status, labels, taints, and other Kubernetes node attributes.
No binary data output is produced by this operation.
Dependencies
- Requires a configured API authentication credential to connect to the Rancher/Kubernetes API.
- The node depends on the Rancher/Kubernetes API being accessible and properly authenticated.
- The node uses internal helper methods to load options dynamically for clusters, projects, and namespaces.
Troubleshooting
Common issues:
- Incorrect or missing cluster ID will cause failure to retrieve nodes.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Specifying a project or namespace that does not exist or is not accessible may return empty results or errors.
Error messages:
- Authentication failures typically indicate misconfigured API credentials.
- "Resource not found" errors may occur if cluster/project/namespace IDs are incorrect.
- Network or connectivity errors suggest issues reaching the Rancher/Kubernetes API endpoint.
Resolutions:
- Verify API credentials and permissions.
- Confirm cluster, project, and namespace identifiers are correct.
- Ensure network access to the Rancher/Kubernetes API server.
Links and References
- Kubernetes Nodes Documentation
- Rancher API Documentation
- n8n Expressions Documentation (for using expressions in property fields)