Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Get All Kubernetes Ingresses

AI-generated

Overview

This node operation retrieves all Kubernetes Ingress resources within a specified namespace of a Kubernetes environment. It is useful for users who want to list or monitor the ingress configurations that control external access to services in their Kubernetes clusters. Practical applications include auditing ingress rules, automating monitoring workflows, or integrating ingress data into dashboards.

Properties

Name Meaning
Id Environment identifier (numeric ID) specifying which Kubernetes environment to query.
Namespace The name of the Kubernetes namespace from which to retrieve all ingress resources.

Output

The output will be a JSON array containing details of all ingress resources found in the specified namespace. Each item in the array represents an ingress object with its metadata and specifications as defined by Kubernetes. This typically includes fields such as ingress name, rules, backend services, TLS settings, and annotations.

If the node supports binary data output, it would likely relate to raw Kubernetes resource manifests or logs, but this is not indicated in the provided code snippet.

Dependencies

  • Requires access to a Kubernetes environment identified by the provided environment ID.
  • Needs proper authentication credentials configured in n8n to connect securely to the Kubernetes API.
  • The node depends on an underlying API client or SDK capable of querying Kubernetes ingress resources.

Troubleshooting

  • Common issues:
    • Invalid or missing environment ID may cause connection failures.
    • Incorrect namespace name can result in empty results or errors.
    • Insufficient permissions on the Kubernetes cluster might prevent listing ingress resources.
  • Error messages:
    • Authentication errors indicate misconfigured or missing API credentials.
    • "Namespace not found" errors suggest the specified namespace does not exist in the cluster.
    • Timeout or network errors imply connectivity problems between n8n and the Kubernetes API server.

Resolving these usually involves verifying credentials, checking namespace spelling, and ensuring network access.

Links and References

Discussion