Re: [prometheus-developers] Re: Helm charts home

[Frederic Branczyk]

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  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.

Re: [prometheus-developers] Re: Helm charts home

[Stuart Clark]

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/2417983d-7501-c3e3-f34f-715792cdbae6%40Jahingo.com.

Re: [prometheus-developers] Re: Helm charts home

[David Karlsen]

+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.



tir. 9. jun. 2020 kl. 12:44 skrev Frederic Branczyk :

> I personally think the amount of things happening in these charts is too
> big to represent "prometheus". Same goes for the prometheus-operator chart.
> Both of these cover a very large surface and as a result issues frequently
> get filed against the upstream projects confusing problems with the charts
> with the scope of the projects themselves.
>
> If a chart was in the community org then it should really only deploy and
> configure Prometheus in my opinion. Meta charts that configure multiple
> sub-charts would be ok, but under a different name (which is why we called
> the project that integrates the two worlds tightly with each other
> kube-prometheus ).
>
> On Thu, 4 Jun 2020 at 23:50, Mingchin Hsieh  wrote:
>
>> Hi guys,
>>
>> I am one of Helm Prometheus chart maintainers:
>>
>>
>> https://github.com/helm/charts/blob/master/stable/prometheus/Chart.yaml#L18
>>
>> I hope I could help to move Helm Prometheus chart for looking new home.
>> If after deprecation date, I will host it on my personal repo.
>>
>> Best,
>> Ming
>>
>> On Tuesday, March 31, 2020 at 11:38:58 AM UTC+8, Naseem Ullah wrote:
>>>
>>> As per the helm charts stable repo deprecation timeline
>>> , the various
>>> prometheus related helm charts such as prometheus
>>> ,
>>>  prometheus-operator
>>> 
>>> , prometheus-adapter
>>> ,
>>> prometheus-node-exporter
>>> 
>>>  and
>>> the various other exporters will require a new home and none more fitting
>>> than https://github.com/prometheus-community.We have had successful
>>> migrations of the sort with other CNCF projects, namely Jaeger (
>>> https://github.com/jaegertracing/helm-charts)  and Fluent Bit(
>>> https://github.com/fluent/helm-charts).
>>>
>> --
>> 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/53909810-686f-4550-977a-4f1c721dc8fao%40googlegroups.com
>> 
>> .
>>
> --
> 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/CAOs1UmwkV8vMu%2BgEZ0kHNnJXMER%2BuNboSr_WxKnAWnv2J40gmA%40mail.gmail.com
> 
> .
>


-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

-- 
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/CAGO7Ob1zAwGihxhjOsDRYDzm8EWbBUweEvt0XzJdWEUmfAe%2BhA%40mail.gmail.com.

Re: [prometheus-developers] Re: Helm charts home

[Frederic Branczyk]

I personally think the amount of things happening in these charts is too
big to represent "prometheus". Same goes for the prometheus-operator chart.
Both of these cover a very large surface and as a result issues frequently
get filed against the upstream projects confusing problems with the charts
with the scope of the projects themselves.

If a chart was in the community org then it should really only deploy and
configure Prometheus in my opinion. Meta charts that configure multiple
sub-charts would be ok, but under a different name (which is why we called
the project that integrates the two worlds tightly with each other
kube-prometheus ).

On Thu, 4 Jun 2020 at 23:50, Mingchin Hsieh  wrote:

> Hi guys,
>
> I am one of Helm Prometheus chart maintainers:
>
> https://github.com/helm/charts/blob/master/stable/prometheus/Chart.yaml#L18
>
> I hope I could help to move Helm Prometheus chart for looking new home. If
> after deprecation date, I will host it on my personal repo.
>
> Best,
> Ming
>
> On Tuesday, March 31, 2020 at 11:38:58 AM UTC+8, Naseem Ullah wrote:
>>
>> As per the helm charts stable repo deprecation timeline
>> , the various
>> prometheus related helm charts such as prometheus
>> ,
>>  prometheus-operator
>> ,
>> prometheus-adapter
>> ,
>> prometheus-node-exporter
>>  
>> and
>> the various other exporters will require a new home and none more fitting
>> than https://github.com/prometheus-community.We have had successful
>> migrations of the sort with other CNCF projects, namely Jaeger (
>> https://github.com/jaegertracing/helm-charts)  and Fluent Bit(
>> https://github.com/fluent/helm-charts).
>>
> --
> 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/53909810-686f-4550-977a-4f1c721dc8fao%40googlegroups.com
> 
> .
>

-- 
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/CAOs1UmwkV8vMu%2BgEZ0kHNnJXMER%2BuNboSr_WxKnAWnv2J40gmA%40mail.gmail.com.