I wasn't saying they don't have their place, I'm saying they both do too much to accurately match their name. The prometheus chart should only be about deploying prometheus, and nothing else, as in no additional exporters etc. and neither should the prometheus-operator chart, it should only deploy the prometheus-operator and nothing else.
There is a place for higher level/meta packages, but not named "prometheus" or "prometheus-operator" is all I'm saying. On Tue, 9 Jun 2020 at 15:43, Stuart Clark <stuart.cl...@jahingo.com> wrote: > On 09/06/2020 13:15, David Karlsen wrote: > > +1 > > Single chart for single components, and then an umbrella-chart can > > bring all of them together - then people can select whatever is most > > appropriate. > > > > > > Prometheus Operator & generic Prometheus are two different things, and > the existing Helm repo reflects that. > > You can use the various individual Helm charts to install Prometheus, > Alertmanager, Grafana and various exporters and then manually plumb > things together. > > Alternatively Prometheus Operator mixes in some extra magic using > slightly customised deployments (using the Prometheus Operator chart) to > allow decentralised configuration using different CRDs (ServiceMonitors > for what to scrape, alert rules, instances, etc.) > > So both have their place. > > -- > Stuart Clark > > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/CAOs1UmzHcEWp6SaPgE0Rg65PXJer0in%3DBDD0Qha8%3DV%3D%3DMh3gQQ%40mail.gmail.com.
