***NOT WORKING: Ingress path based routing

===Issue
I do not understand what is the point of having ingress if it's nearly impossible to put an application under a domain path. Like domain.com/nextcloud . Putting nextcloud on domain.com is easy, sub.domain.com also easy, but on domain.com/nextcloud is nearly impossible.

is it not the main purpose to have helm so we can deploy these apps pretty easilly? And have API or ingress so we can put these apps under URL paths?

===Expectation
Easy working method to put nextcloud under domain.com/nextcloud

===Error
Any way I try it, it always gives some error...

===What was tried
Tried solutions from half the internet. A variety of rewriting rules, ingress config in this helm, separate ingress config. Literally not 1 thing works

===Questioning
Why make applications so difficult. Why is it not the norm to have 1 easy setting to have the app at whatever path we want. I see only unnecessary complication.

Start by reviewing the Helm chart's ingress configuration and reproducing the requested Nextcloud deployment at domain.com/nextcloud. Done means there is a documented, working path-based routing setup that does not produce the reported errors.