Allow customizing ingress type and pathType directly in the mattermost spec

[finda-yeongjo]

Allow customizing ingress type and pathType directly in the mattermost spec

[fmartingr]

I'm not currently aware of the roadmap, but ideally we could allow customising the ingress in the Mattermost spec by adding the path and pathType fields. I'm going to update the issue title to reflect the actual issue. And of course pull requests are welcome.

[0arko]

i think i may have also ran into this issue. What do your listener rules look like? I had to manually edit the listener rule condition to accept '/*' as opposed to '/'. As this ingress is deployed via the Mattermost operator, after some time or a redeploy the listener rule reverts back and we see the 404 again. I still haven't worked out a way to specify the wildcard in the path via the Mattermost installation manifest file though...

[fmartingr]

is there a way to edit the path that the aws ingress controller uses via the mattermost installation?

Not at the moment, the path is static in the code.

[finda-yeongjo]

If what @0arko said is correct, I request that @fmartingr modify the "pathType" of the Mattermost ingress to "Prefix."
Here are my ingress desire manifests that are working correctly and a capture of the current problematic Mattermost ingress. You will easily understand what I mean.

[0arko]

is there a way to edit the path that the aws ingress controller uses via the mattermost installation?

[0arko]

thanks @fmartingr is there any chance this will be configurable any time soon? or at least made static to /* for instance