Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node integrates with Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically. It supports multiple resource types such as namespaces, deployments, services, pods, statefulsets, configmaps, secrets, jobs, cronjobs, and nodes. The "Get" operation for the "Node" resource allows users to retrieve information about one or more nodes within a specified cluster.
Common scenarios where this node is beneficial include:
- Automating infrastructure management tasks in Kubernetes clusters.
- Retrieving detailed node information for monitoring or auditing purposes.
- Integrating Kubernetes node data into workflows for decision-making or reporting.
For example, you can use this node to fetch details of a specific node by its ID within a given cluster, project, and namespace, enabling automated checks on node status or labels before deploying workloads.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster from which to get the node information. Can be chosen from a list or specified via expression. |
| Project Name or ID | Select the project within the cluster. Depends on the selected cluster. Can be chosen from a list or specified via expression. |
| Namespace Name or ID | Select the namespace within the project. Depends on the selected project. Can be chosen from a list or specified via expression. |
| Node ID | The unique identifier of the node to retrieve information about. Required for node operations. |
Output
The output is a JSON object containing the retrieved node information as returned by the Rancher/Kubernetes API. This typically includes details such as node metadata, status, labels, taints, capacity, and other relevant properties describing the node's configuration and state.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"metadata": {
"name": "node-name",
"labels": { "key": "value" },
...
},
"status": {
"capacity": { "cpu": "4", "memory": "16Gi" },
"conditions": [...],
...
},
...
}
Dependencies
- Requires an API authentication token credential configured in n8n to connect securely to the Rancher/Kubernetes API.
- The node depends on the Rancher/Kubernetes API being accessible and properly configured with the necessary permissions to read node information.
- The node uses internal methods to load options dynamically for clusters, projects, and namespaces.
Troubleshooting
- Missing or invalid credentials: Ensure that the API key or authentication token is correctly set up and has sufficient permissions to access node information.
- Invalid Cluster/Project/Namespace selection: Verify that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
- Node ID not found: Confirm that the specified node ID exists in the selected cluster and project.
- API connectivity issues: Check network connectivity and Rancher/Kubernetes API endpoint availability.
- Permission errors: Make sure the API user has the required RBAC permissions to perform "get" operations on nodes.