502 error with ingress-nginx using the -next chart

[p4block]

trafficstars

Describe the bug My ingress controller was returning 502 when accessing the domain.

To Reproduce Install the chart on a ingress-nginx cluster (may be gke only?)

Expected behavior Login page appears

Additional context Works after adding these annotations (may not be optimal at all)

    nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
    nginx.ingress.kubernetes.io/proxy-buffers: "8 16k"

This comment gave me the tip. I don't think I would've have found it.

What ingress controller are you using for your own internal tests? I also analyzed the page and nothing overly huge is loaded. Pretty weird. Interaction with the frontend server?

[Nathanael-Mtd]

Personally, at work, we use Traefik and we don't need other annotations. I think that's a frontend code issues, I found something with same report here : https://github.com/intuitem/ciso-assistant-community/issues/803#issuecomment-2357798851

[geomtech]

Got the same issue, thanks for the tip, it's helping but, it's really slow for our instance. Do you have any tips?