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. Specifically, for the Deployment - Get operation, it retrieves information about one or more deployments within a specified Kubernetes namespace. This is useful for monitoring deployment status, inspecting configuration details, or automating workflows that depend on deployment metadata.
Common scenarios include:
- Fetching deployment details to verify rollout status.
- Automating audits of deployed applications.
- Integrating deployment data into dashboards or reports.
Example: You might use this node to get the current state of a deployment named "web-app" in a particular namespace to check if the desired number of replicas are running.
Properties
| Name | Meaning |
|---|---|
| Cluster Name or ID | Select the Kubernetes cluster from which to retrieve the deployment. 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 where the deployment resides. Can be chosen from a list or specified via expression. |
These properties are required to scope the request correctly to the target deployment(s).
Output
The output is a JSON object representing the deployment(s) retrieved from the Kubernetes API. The structure typically includes metadata (like name, labels, annotations), specification details (such as container images, replicas), and status information (current state, available replicas, conditions).
The output is returned as an array of items, each with a json property containing the deployment data.
No binary data is produced by this operation.
Dependencies
- Requires an API authentication token or key credential configured in n8n to access the Rancher/Kubernetes API.
- The node depends on the Rancher/Kubernetes API being accessible and properly configured with the provided credentials.
- The cluster, project, and namespace must exist and be accessible with the given credentials.
Troubleshooting
- Missing or invalid credentials: Ensure the API key or token is valid and has sufficient permissions to read deployments.
- Incorrect cluster/project/namespace selection: Verify that the selected cluster, project, and namespace exist and are spelled correctly.
- Network connectivity issues: Confirm that n8n can reach the Rancher/Kubernetes API endpoint.
- API rate limits or permission errors: Check API quotas and user permissions if requests fail with authorization errors.
- Empty results: If no deployments are returned, confirm that deployments exist in the specified namespace.
Links and References
- Kubernetes Deployments Documentation
- Rancher API Documentation
- n8n Expressions Documentation (for using expressions in property fields)