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
If Kubediag is behind a reverse proxy, particularly one where Kubediag is not at the root, this doesn't work so well.
For example, I have Nginx installed with the following configuration:
This configuration would serve Kubediag up on http://localhost:30066/kubediag/, and Nginx will include the /kubediag/ prefix when passing on requests to Kubediag. To make this work we should enable route prefix feature which will allow to control this more granularly:
kubediag-dashboard --web.route-prefix=/kubediag
The text was updated successfully, but these errors were encountered:
If Kubediag is behind a reverse proxy, particularly one where Kubediag is not at the root, this doesn't work so well.
For example, I have Nginx installed with the following configuration:
This configuration would serve Kubediag up on http://localhost:30066/kubediag/, and Nginx will include the /kubediag/ prefix when passing on requests to Kubediag. To make this work we should enable route prefix feature which will allow to control this more granularly:
The text was updated successfully, but these errors were encountered: