Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Update Kubernetes Ingress Controllers By Namespace

AI-generated

Overview

This node operation updates Kubernetes Ingress Controllers within a specified namespace. It is useful for managing and modifying the configuration of ingress controllers that route external traffic to services inside a Kubernetes cluster. Typical use cases include updating routing rules, TLS settings, or other ingress controller parameters programmatically as part of CI/CD pipelines or automated infrastructure management.

For example, you might use this node to update ingress controllers after deploying a new version of an application, ensuring that traffic is correctly routed without manual intervention.

Properties

Name Meaning
Id Environment identifier; a numeric ID representing the target Kubernetes environment.
Namespace The name of the Kubernetes namespace where the ingress controllers reside.
Body JSON string representing the ingress controllers' configuration to be updated.

Output

The node outputs JSON data reflecting the result of the update operation on the ingress controllers. This typically includes status information, confirmation of changes applied, or error details if the update failed.

If the node supports binary data output (not indicated here), it would represent related files or artifacts returned by the API, but in this case, the output is purely JSON.

Dependencies

  • Requires access to a Kubernetes environment with appropriate permissions to update ingress controllers.
  • Needs an API key or authentication token configured in n8n credentials to authenticate requests against the Kubernetes API or a proxy service managing Kubernetes resources.
  • The node uses HTTP requests with JSON payloads to communicate with the Kubernetes API or an intermediary service.

Troubleshooting

  • Common issues:
    • Incorrect namespace or environment ID may cause the update to fail or target the wrong resources.
    • Malformed JSON in the "Body" property can lead to request rejection.
    • Insufficient permissions or expired/invalid API credentials will prevent successful updates.
  • Error messages:
    • Authentication errors indicate problems with the API key or token; verify credentials and permissions.
    • Validation errors usually point to incorrect or incomplete ingress controller configurations in the body; ensure JSON syntax and required fields are correct.
    • Network or connectivity errors suggest issues reaching the Kubernetes API endpoint; check network settings and base URL configuration.

Links and References

Discussion