search

8gears / n8n-helm-chart

A Kubernetes Helm chart for n8n - a workflow automation tool. Easily automate tasks across different services on self hosted onKubernetes
https://artifacthub.io/packages/helm/open-8gears/n8n
Apache License 2.0
208 stars 104 forks source link

Setting scaling.enabled along with scaling.webhooks.enabled results in web hook endpoint returning 404 or 502 #122

Open knuurr opened 4 weeks ago

knuurr commented 4 weeks ago

We're experimenting with introducing at least some HA to our workflow processing, as very often we experience that main n8n pod is hanging and needs manual restart (and sometimes workers too).

This is our current, working setup:

            extraEnv:
              WEBHOOK_URL: "https://n8n.domain.com/"
               ....
            scaling:
              enabled: true
              worker:
                count: 2
                concurrency: 2
              webhook:
                enabled: false
                count: 1
              redis:
                host: <redis url>
                password: <redis pwd>

In normal condition, when we try to POST our webhook endpoint, everything is ok and status is 200

curl -I -X POST https://n8n.domain.com/webhook/someendpoint
HTTP/2 200 
date: Mon, 28 Oct 2024 15:34:30 GMT
content-type: application/json; charset=utf-8
...

As I introduce changes to values in chart, setting scaling.webhook.enabled to true, the same endpoint can no longer be accessed, with returning 404 or502 (not sure what it depends on yet - but it doesn't work)

            scaling:
              enabled: true
              worker:
                count: 2
                concurrency: 2
              webhook:
                enabled: true # change
                count: 1
              redis:
                host: <redis url>
                password: <redis pwd>
curl -I -X POST https://n8n.domain.com/webhook/someendpoint
HTTP/2 404 
date: Mon, 28 Oct 2024 15:33:10 GMT
content-type: text/html; charset=utf-8
....

We also see the same in our endpoint monitoring tool that once change is live, monitoring fails.

I'm not entirely sure if this is a question related to chart, or general n8n question. But since we use this chart for deployment I decided that maybe asking here is a good start.

What are we doing wrong here? If any info is missing I will happily provide

n8n Version 1.40.0