In case of add new tenant in config file (CM and secret in my case), the application need to be restarted to reload the configuration. That cause a "connection reset by peer" or something like this on client side and can become a problem when user get a long query to Loki from Grafana for example.
I think we need to implement an endpoint to reload config like prometheus does and create a config reloader sidecar to call this endpoint in case of update of the config files.
You will try to work on this but if you can tell me your things about this and the right path to implement it, tell me !
Hi,
In case of add new tenant in config file (CM and secret in my case), the application need to be restarted to reload the configuration. That cause a "connection reset by peer" or something like this on client side and can become a problem when user get a long query to Loki from Grafana for example.
I think we need to implement an endpoint to reload config like prometheus does and create a config reloader sidecar to call this endpoint in case of update of the config files.
You will try to work on this but if you can tell me your things about this and the right path to implement it, tell me !