Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Create Kubernetes Ingress

AI-generated

Overview

This node operation allows you to create a Kubernetes Ingress resource within a specified namespace. Kubernetes Ingress manages external access to services in a cluster, typically HTTP. By creating an Ingress, you define rules for routing external traffic to internal services based on hostnames or paths.

Common scenarios include exposing web applications running inside Kubernetes clusters to the internet, managing SSL termination, and load balancing HTTP traffic.

For example, you might use this node to programmatically create an Ingress that routes requests from example.com to a backend service running in your cluster, enabling automated deployment workflows or dynamic environment setups.

Properties

Name Meaning
Id Environment identifier (a numeric ID representing the target Kubernetes environment).
Namespace The Kubernetes namespace where the Ingress resource will be created.
Body JSON string containing the full specification of the Ingress resource to create. This includes metadata, spec, rules, and other Kubernetes Ingress details.

Output

The node outputs the response from the Kubernetes API after attempting to create the Ingress resource. The output is structured as JSON and typically contains the created Ingress object details, including metadata like name, namespace, UID, creation timestamp, and the spec confirming the applied configuration.

If the creation is successful, the output JSON reflects the newly created Ingress resource. If there is an error, the output will contain error information returned by the Kubernetes API.

This node does not handle binary data output.

Dependencies

  • Requires access to a Kubernetes cluster API endpoint.
  • Needs appropriate authentication credentials (such as a token or certificate) configured in n8n to authorize API requests.
  • The user must provide the Ingress resource definition in valid JSON format.
  • Network connectivity to the Kubernetes API server is necessary.

Troubleshooting

  • Invalid JSON in Body: If the Ingress body JSON is malformed, the Kubernetes API will reject the request. Ensure the JSON is valid and matches Kubernetes Ingress schema.
  • Authentication Errors: Failure to authenticate with the Kubernetes API will result in authorization errors. Verify that the API credentials are correct and have sufficient permissions to create Ingress resources.
  • Namespace Not Found: Specifying a non-existent namespace will cause the API to return an error. Confirm the namespace exists before creating the Ingress.
  • API Server Connectivity: Network issues or incorrect API server URL can cause connection failures. Check network settings and base URL configuration.
  • Resource Conflicts: Attempting to create an Ingress with a name that already exists may cause conflicts. Use unique names or update existing resources accordingly.

Links and References

Discussion