Allow users to use custom config maps for components like weave's prometheus
bricef opened this issue · comments
Problem: Our default configuration of prometheus scrapes everything by default. This results if exceptionally noisy logs. In addition, customers desire our prometheus to be configurable to scrape things outside of the cluster.
When manually changing the configmap, the launcher agent will reset the configuration back, erasing user changes.
How do we enable custom configuration of our launcher-shipped prometheus instance.
(usecase is monitoring a legacy mongodb cluster running outside K8s)
