Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Get All Kubernetes Ingress Controllers

AI-generated

Overview

This node operation retrieves a list of Kubernetes Ingress Controllers from a specified environment. It is useful for users who want to programmatically access and manage ingress controllers within their Kubernetes clusters, such as for monitoring, auditing, or automation purposes.

A practical example would be an automation workflow that fetches all ingress controllers allowed in a particular Kubernetes environment to verify compliance with security policies or to update routing rules dynamically.

Properties

Name Meaning
Id Environment identifier (a numeric ID) specifying which Kubernetes environment to query.
Additional Fields Optional extra parameters to refine the request:
- Allowed Only Boolean flag to return only ingress controllers that are allowed (true/false).

Output

The output contains a JSON array listing Kubernetes ingress controllers retrieved from the specified environment. Each item in the array represents an ingress controller with its associated metadata as provided by the Kubernetes API or the underlying service.

No binary data output is indicated.

Dependencies

  • Requires connection to a Kubernetes environment identified by the provided environment ID.
  • The node likely depends on an API key or authentication token configured in n8n credentials to access the Kubernetes cluster or intermediary service managing the ingress controllers.
  • No explicit external libraries or services are referenced beyond standard HTTP API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing environment ID may cause failure to retrieve ingress controllers.
    • Insufficient permissions or incorrect API credentials can lead to authorization errors.
    • Network connectivity problems between n8n and the Kubernetes environment will prevent data retrieval.
  • Error messages:

    • Authorization errors typically indicate invalid or missing API credentials; ensure correct setup of authentication tokens.
    • "Environment not found" or similar errors suggest the provided environment ID does not exist or is inaccessible.
    • Timeout or network errors require checking connectivity and firewall settings.

Links and References

Discussion