You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As helm-dashboard is built in a / context, it's difficult, in a multipaths context, to rewrite the / routes from helm-dashboard to a dedicated subpath (as / matches all the apps under it).
However, if helm-dashboard is built in a default /helm-dashboard context (or something else), it would be a lot easier to rewrite the /helm-dashboard routes to another dedicated subpath.
I know my idea is a big change, but can it be a possible solution ?
Description
The helm-dashboard seems to only respond on a
/
context.I want helm-dashboard to respond from my.domain.com/helm-dashboard.
Screenshots
Additional information
As stated in the ingress-nginx documentation, I deployed helm-dashboard like this :
Here is the result of the Ingress object deployed :
Subsequently, I would like to set up oauth2 authentification.
The text was updated successfully, but these errors were encountered: