Actions40
- Node Actions
- Namespace Actions
- Deployment Actions
- Service Actions
- Pod Actions
- StatefulSet Actions
- ConfigMap Actions
- Secret Actions
- Job Actions
- CronJob Actions
Overview
This node allows interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources. Specifically, for the Pod resource with the Get operation, it retrieves information about one or more pods within a specified Kubernetes namespace.
Common scenarios where this node is beneficial include:
- Monitoring pod status and metadata in a Kubernetes cluster.
- Automating workflows that require fetching pod details dynamically.
- Integrating Kubernetes pod data into broader automation pipelines.
For example, you can use this node to fetch all pods running in a particular namespace of a project within a cluster, then process their statuses or logs downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster from which to retrieve pods. 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. |
| Namespace Name or ID | Select the namespace within the project to scope the pod retrieval. |
These properties are required to specify the exact location in the Kubernetes hierarchy (cluster → project → namespace) where the pods reside.
Output
The output is an array of JSON objects representing the retrieved pod(s). Each object contains detailed information about a pod as returned by the Rancher/Kubernetes API, including metadata, status, and specifications.
The json field holds this pod data structure. The node does not output binary data for this operation.
Dependencies
- Requires access 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 populate options for clusters, projects, and namespaces.
Troubleshooting
- Missing or invalid cluster/project/namespace selection: 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 credential is valid and has sufficient permissions to read pod information.
- Empty results: Confirm that pods exist in the specified namespace; otherwise, the output will be empty.
- Network connectivity issues: Check network access to the Rancher/Kubernetes API endpoint.