Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

[FEATURE] reverse_proxy role to access all UIs deployed #64

Open
strus38 opened this issue May 4, 2022 · 0 comments
Open

[FEATURE] reverse_proxy role to access all UIs deployed #64

strus38 opened this issue May 4, 2022 · 0 comments

Comments

@strus38
Copy link
Contributor

strus38 commented May 4, 2022

It would be nice to have a generic role to be able to deploy a reverse_proxy allowing to attach the UI we deliver such as prometheus/grafana/karma or any other.
Of course this reverse proxy should be able to be runing on a login node or the magaement node (using the VIP of the HA if there).
Also the reverse proxy should be using FQDNs to be compatible with an optionnal installation of a OIDC provider.
There are 2 solutions:

  • Using the existing httpd server used to distribute the softwares
  • Using another instance of this httpd server to be installed for this purpose on another server than the mgmt server.

The role should accept config file to add rules in this reverse-proxy.

The defaut path of the reverse proxy, http(s)://./index.html should be able to list all services available, those services could be installed as:

  • http(s)://./ (like: http(s)://./grafana, http(s)://./prometheus)
    or
  • http(s)://. (like: http(s)://grafana,

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant