Rancher27 icon

Rancher27

Interact with Rancher/Kubernetes API
Join our community

Actions40

Overview

This node enables interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources programmatically within n8n workflows. Specifically, for the Job resource with the Get operation, it retrieves information about one or more Kubernetes Jobs within a specified namespace of a project and cluster.

Common scenarios where this node is beneficial include:

  • Monitoring the status and details of batch jobs running in Kubernetes clusters.
  • Automating retrieval of job metadata for reporting or triggering downstream processes.
  • Integrating Kubernetes job data into broader automation workflows without manual API calls.

For example, you can use this node to fetch all jobs in a particular namespace to check their completion status or to get detailed job specifications for auditing purposes.

Properties

Name Meaning
Cluster Name or ID Select the Kubernetes cluster by name or ID where the job resides.
Project Name or ID Select the project within the cluster that contains the namespace.
Namespace Name or ID Select the namespace within the project where the job is located.

These properties are required to scope the request correctly to the desired Kubernetes Job resource.

Output

The output is a JSON object representing the retrieved Job(s) data from the Kubernetes API. This typically includes fields such as job metadata (name, labels, annotations), status (active, succeeded, failed counts), specifications (template, parallelism, completions), and other relevant Kubernetes Job details.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "metadata": {
    "name": "example-job",
    "namespace": "default",
    "labels": { "app": "my-app" }
  },
  "status": {
    "active": 1,
    "succeeded": 0,
    "failed": 0
  },
  "spec": {
    "parallelism": 1,
    "completions": 1,
    "template": { /* pod template spec */ }
  }
}

Dependencies

  • Requires an active connection to a Rancher/Kubernetes cluster via an API authentication token configured in n8n credentials.
  • The node depends on Rancher/Kubernetes API endpoints being accessible and properly authorized.
  • The user must have appropriate permissions to read Job resources in the specified namespace.

Troubleshooting

  • Missing or invalid cluster/project/namespace selection: Ensure that the selected cluster, project, and namespace exist and are accessible. Use the provided dropdowns or valid IDs.
  • API authentication errors: Verify that the API key or token credential used has sufficient permissions to query Job resources.
  • Network connectivity issues: Confirm that n8n can reach the Rancher/Kubernetes API endpoint.
  • Empty or no results: Check if there are any Jobs deployed in the specified namespace; otherwise, the output will be empty.
  • Permission denied errors: Make sure the service account or user associated with the API token has read access to Jobs in the target namespace.

Links and References

Discussion