-
Notifications
You must be signed in to change notification settings - Fork 203
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Did you check docs and existing issues?
- I have read the n8n Helm chart documentation
- I have updated the Helm chart to the latest version before submitting this issue
- I have searched the existing issues of n8n
- I have searched the existing issues of related Kubernetes/Helm components
n8n version
1.112.0
Helm chart version
1.0.15
Kubernetes version
1.31.1
Helm version
3.19.0
Operating system/platform
Oracle cloud
Describe the bug
When deploying the n8n Helm chart, the generated Ingress uses:
- path: /
pathType: Prefix
backend:
service:
name: n8n
port:
number: 80
On some ingress controllers this configuration does not route requests to /
correctly.
As a result, the n8n web UI is inaccessible at the root path.
Replacing the root rule with:
Replacing the root rule with:
- pathType: ImplementationSpecific
backend:
service:
name: n8n
port:
number: 80
or moving the root service to defaultBackend
resolves the issue.
Steps To Reproduce
- Install the n8n Helm chart with the following values:
ingress:
enabled: true
hosts:
- host: "host"
paths: ["/"]
- Try to open the n8n web UI at
https://<host>/
. - Observe that the UI is not accessible.
Expected Behavior
The root path (/
) should route correctly across different ingress controllers, not only ingress-nginx.
Helm values.yaml
Kubernetes logs
Additional context
This affects environments where pathType: Prefix
for /
is not supported or behaves differently than in ingress-nginx.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working