PortainerInstall

Overview

This node operation updates an existing Kubernetes Ingress resource within a specified namespace. It is useful for modifying the configuration of ingress controllers that manage external access to services in a Kubernetes cluster. Common scenarios include changing routing rules, updating TLS settings, or adjusting backend service references without recreating the ingress from scratch.

For example, you might use this node to update the hostnames or paths that an ingress listens to, or to add new annotations required by your ingress controller.

Properties

Output

The node outputs the JSON response returned by the Kubernetes API after updating the ingress resource. This typically includes the updated ingress object with its current state and metadata.

If the node supports binary data output, it is not indicated here; the main output is JSON reflecting the updated ingress resource.

Dependencies

• Requires access to a Kubernetes cluster API endpoint.
• Needs appropriate authentication credentials (e.g., API token) configured in n8n to authorize requests against the Kubernetes API.
• The node sends HTTP requests to the Kubernetes API server, so network connectivity and permissions are necessary.

Troubleshooting

• Invalid or missing Id: Ensure the environment identifier corresponds to a valid Kubernetes cluster configuration.
• Namespace not found: Verify the namespace exists in the target cluster.
• Malformed Body JSON: The body must be a valid JSON string representing the ingress resource. Invalid JSON will cause request failures.
• Authorization errors: Check that the API credentials have sufficient permissions to update ingress resources.
• Resource not found: If the ingress with the specified name does not exist in the namespace, the update will fail.
• API server connectivity issues: Network problems or incorrect API URLs can prevent successful updates.

Links and References

• Kubernetes Ingress API Reference
• Kubernetes Ingress Concepts
• Kubernetes API Authentication