consul ui ingress resource only works if set to /

[vtuson]

I tried many many combinations of annotations but basically consul-ui always redirects to to /ui/ so the only way to get the ingress to work (that I have found) is to math path / (wont work for example if you make it /consul/)

This is due to a long standing issue with consul, seems that was fixed but broke again with the new UI - hashicorp/consul#1930

Also it might be possible to work around this added a custom config snippet (https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md#configuration-snippet) but I dont know enough about nginx to suggest a solution

[juan131]

Hi @vtuson

Thanks for opening this issue! It seems there's no way to configure the UI path on the application itself, therefore, it's sth we could fix by adding some kind of env. variable to the container to use a custom path for the UI.

As you mentioned, a possible workaround would be using a configuration snippet so we can modify the way NGINX handle the proxy redirection.

However, this configuration snippet will be including on the Ingress annotations (which are different depending on the Ingress solution you're using). Hence, my doubts about this approach. We could add some annotations for NGINX BUT they will be ignored by other Ingress Controllers...

[vtuson]

you are right, that they wouldnt be generic, not sure if it is worth adding nginx as it is the standard upstream provided or not? but might be worth documenting it in the readme

[juan131]

What do you think @sameersbn @prydonius ?

[prydonius]

Perhaps the simplest thing for now is to document that Consul UI can only be exposed on the root in an Ingress. FYI, we have the same issue in Kubeapps, the Dashboard currently cannot be mounted in a subpath due to the way the React app loads things and uses routes.

[juan131]

Are you ok with just documenting it @vtuson ? We could also modify the NOTES.txt so we show a warning in case we detect someone is using a different path on the Ingress Rule.

[stale]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[stale]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[mumubin]

Is there a solution？

[juan131]

Hi @mumubin

We didn't document anything so far. There are other users requesting similar features for other charts. If you take a look to the issue below, you'll find out there's a way to play with Ingress annotations so you add extra configuration with redirections:

helm/charts#17196