Rancher icon

Rancher

Interact with Rancher/Kubernetes API

Actions54

Overview

This node allows interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources. Specifically, for the Service resource with the Get operation, it retrieves information about one or more services within a specified cluster, project, and namespace.

Common scenarios where this node is beneficial include:

  • Automating retrieval of service details in a Kubernetes environment managed by Rancher.
  • Integrating Kubernetes service data into workflows for monitoring, reporting, or further automation.
  • Dynamically fetching service configurations to trigger conditional logic or updates in other systems.

For example, you could use this node to get all services running in a particular namespace of a cluster to audit their configurations or to feed service endpoints into downstream automation tasks.

Properties

Name Meaning
Cluster Name or ID Select the Kubernetes cluster from which to retrieve the service(s). Can be chosen from a list or specified via expression. (Required)
Project Name or ID Optionally select the project within the cluster. Can be chosen from a list or specified via expression.
Namespace Name or ID Optionally select the namespace within the project. Can be chosen from a list or specified via expression.

These properties define the scope of the service query: the cluster, project, and namespace context.

Output

The node outputs an array of JSON objects representing the retrieved service(s). Each object contains detailed information about a Kubernetes service, such as metadata, specifications, and status fields as returned by the Rancher/Kubernetes API.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "json": {
      "metadata": {
        "name": "my-service",
        "namespace": "default",
        "labels": { ... },
        "annotations": { ... }
      },
      "spec": {
        "type": "ClusterIP",
        "ports": [ ... ],
        "selector": { ... }
      },
      "status": {
        "loadBalancer": { ... }
      }
    }
  }
]

Dependencies

  • Requires a configured Rancher/Kubernetes API credential with appropriate permissions to access the cluster, project, and namespace.
  • The node depends on Rancher's API endpoints to fetch service data.
  • The user must configure the node with valid cluster, project, and namespace identifiers.

Troubleshooting

  • Missing or invalid cluster/project/namespace: Ensure that the selected cluster, project, and namespace exist and are accessible with the provided credentials.
  • Permission errors: The API credential used must have read access to the targeted resources; otherwise, authorization errors will occur.
  • Empty results: If no services are found, verify that the namespace and project parameters are correct and that services actually exist there.
  • API connectivity issues: Network problems or incorrect API endpoint configuration can cause failures; check connectivity and credential validity.

Links and References

Discussion