Deploying using nginx ingress results in 404 for /browser

[spwoodcock]

Background

• Follow on from fix(helm): redirect bare /browser to /browser/ on traefik #544 which fixes this for traefik. Related issue browser.ingress.path (/browser) returns 404 : no redirect to /browser/ #545.
• For templates/networking/ingress.yaml we don't have the same skipStripPrefix param.
• Using nginx ingress, any browser path that isn't / gets the regex form and rewrite-target: /$2, meaning the prefix is always stripped, and we get a 404. I verified browser.ingress.path=/browser results in the same.
• It's possible to work around this by deploying a standalone Ingress for the browser, alongside the eoAPI chart.

Goals

• Allow viewing /browser with nginx ingress and the default eoAPI chart.

Possible solution

Mirror the Traefik behaviour, where the browser is excluded from strip-prefix and gets its own redirect middleware.

Two changes in templates/networking/ingress.yaml:

1. Honour skipStripPrefix in the nginx path helper as the Traefik template already does, so the browser renders as pathType: Prefix, path: /browser.

2. Render that path in a separate {{ .Release.Name }}-browser-ingress without rewrite-target / use-regex. Those are Ingress-scoped, so in the shared resource /browser is still rewritten to / (empty $2) even without the regex.

I would understand if this won't be accepted, as nginx ingress is deprecated. We should probably be targeting the Gateway API for future changes instead.

I'm happy to PR for this otherwise 👍

[pantierra]

Thanks @spwoodcock for this bug report! Sorry for answering late, just came back from vacations.

We are currently working on this part with the recent developments in the 0.15.2 and #586. Will have a look at this particular case. You may want to try version 0.15.2 to see if the problem still persists.

[spwoodcock]

No worries at all - I hope the info helped!

Feel free to close if you believe it's fixed. I'll give it a test asap to confirm👍