We want to self host novu on our cluster, but having some difficulties. The helm approach is not working, so i made deployment file from the docker-compose.yaml
Now things seem to work, but when i put an ingress in front of the whole setup there are some problems.
The login page comes up, but when it tries to communicate with the api pod via ingress i'm getting 404..
i guess something with the ingress routing but cant figure it out.
Here is the relevant part of the ingress:

creationTimestamp: "2024-03-06T13:12:40Z"
generation: 9
name: novu-ingress
namespace: novu
resourceVersion: "331343269"
uid: b5fc4181-8da5-4e58-9e00-48e2546a9c78
spec:
ingressClassName: nginx-ingress
rules:

host: novu.domain.com
http:
paths:
- backend:
  service:
  name: novu-web-service
  port:
  number: 4200
  path: /
  pathType: Prefix
- backend:
  service:
  name: novu-api-service
  port:
  number: 3000
  path: /v1
  pathType: Prefix

torpid mantle Mar 8, 2024, 2:36 PM

#

I would look at setting up the reverse proxy variables here https://docs.novu.co/self-hosting-novu/deploy-with-docker#reverse-proxy-load-balancers

However this is not something we officially support at this moment but we should be releasing an official helm chart soonish.

crimson wasp Mar 8, 2024, 3:05 PM

#

it is like the API_CONTEXT_PATH dosent affect anything. i set it to api-something but the frontend is still trying to connect to subdomain.domain.com/v1

#

novu-web-85685fd5d6-lk4dl:/app$ env | grep API_CONTEXT
API_CONTEXT_PATH=api-something

#