Open dirkckau opened 3 months ago
Thanks for the issue.
I think this is a good idea, we should do this IMHO.
Plugins really should generally be able to be configured via the helm chart, and env vars. I know we've talked about this before, but we should think it through more. Considering other plugins as well.
I noticed there's a request to disable the prometheus plugin entirely in the already built image here: https://github.com/headlamp-k8s/headlamp/issues/1661
(Disabling plugins entirely is a way of configuring them too.)
In particular Headlamp Pod/Deployment/Statement page, there is a graph to display the resource usage. In certain Kubernetes cluster environments where multiple Prometheus instances serve different purposes, could the Headlamp helm chart offers a configuration option to specify the desired Prometheus instance for Headlamp's query?
In our environment, we met an issue that Headlamp is always query from a wrong Prometheus and we couldn't see a way to configure it.