Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Get Kubernetes Ingress Controllers By Namespace

AI-generated

Overview

This node operation retrieves Kubernetes Ingress Controllers within a specified namespace. It is useful for users who want to programmatically access and manage ingress controllers scoped to a particular namespace in their Kubernetes cluster. Typical scenarios include monitoring ingress controllers, automating deployment checks, or integrating ingress data into workflows.

For example, a DevOps engineer might use this node to fetch all ingress controllers in the "production" namespace to verify configurations or trigger alerts if certain ingress controllers are missing or misconfigured.

Properties

Name Meaning
Id Environment identifier (a numeric ID) specifying which Kubernetes environment to query.
Namespace The Kubernetes namespace from which to retrieve ingress controllers.

Output

The output will contain JSON data representing the list of ingress controllers found in the specified namespace. Each item typically includes details such as the ingress controller's name, configuration, status, and related metadata.

If the node supports binary data output, it would generally relate to any associated certificates or configuration files linked to the ingress controllers, but this is not explicitly indicated here.

Dependencies

  • Requires connection to a Kubernetes environment identified by the provided environment ID.
  • Needs appropriate API authentication credentials configured in n8n to access the Kubernetes API.
  • The node depends on the Kubernetes API being accessible and responsive for the given environment and namespace.

Troubleshooting

  • Common issues:

    • Invalid or missing environment ID can cause failure to connect to the Kubernetes cluster.
    • Incorrect namespace name may result in empty results or errors.
    • Insufficient permissions or expired credentials can lead to authorization errors.
    • Network connectivity problems between n8n and the Kubernetes API endpoint.
  • Error messages:

    • "Unauthorized" or "Forbidden": Check API credentials and permissions.
    • "Namespace not found": Verify the namespace exists in the target cluster.
    • "Connection timed out": Ensure network access to the Kubernetes API server.

Resolving these usually involves verifying credentials, namespace correctness, and network settings.

Links and References

Discussion