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

2020-06-13 Thread Naseem Ullah
The Prometheus chart clearly has optional installable sub chart for ksm: 
https://github.com/helm/charts/blob/master/stable/prometheus/requirements.yaml
We can factor our alertmanager with this chart I've prepared: 
https://github.com/naseemkullah/naseem-charts/tree/master/charts/alertmanager
We can also factor our node exporter with either a new node-exporter chart 
or 
https://github.com/helm/charts/tree/master/stable/prometheus-node-exporter

We are ready to get going, I've had success migrating other CNCF charts 
such as https://github.com/jaegertracing/helm-charts and 
https://github.com/fluent/helm-charts/tree/master/charts/fluent-bit

Please allow me to lead this effort by providing an empty helm-charts repo 
under https://github.com/prometheus-community.

After we have prometheus, node-exporter, alertmanager and the various 
communicty maintained exporter charts hosted, we can discuss a way forward 
for prometheus operator such that Frederic is on board.

On Tuesday, June 9, 2020 at 12:15:27 PM UTC-4, Frederic Branczyk wrote:
>
> 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/4561bda4-af10-4e16-a035-e3173cefe2bdo%40googlegroups.com.


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

2020-06-13 Thread Naseem Ullah
The Prometheus chart clearly has optional installable sub chart for ksm: 
https://github.com/helm/charts/blob/master/stable/prometheus/requirements.yaml
We can factor our alertmanager with this chart I've prepared: 
https://github.com/naseemkullah/naseem-charts/tree/master/charts/alertmanager
We can also factor our node exporter with either a new node-exporter chart 
or 
https://github.com/helm/charts/tree/master/stable/prometheus-node-exporter

We are ready to get going, I've had success migrating other CNCF charts 
such as https://github.com/jaegertracing/helm-charts and 
https://github.com/fluent/helm-charts/tree/master/charts/fluent-bit

Please allow me to lead this effort by providing an empty helm-charts repo 
under https://github.com/prometheus-community.

After we have prometheus, node-exporter, alert-manager and the various 
exporter charts hosted, we can discuss prometheus operator with to be such 
that Frederic is on board.

On Tuesday, June 9, 2020 at 12:15:27 PM UTC-4, Frederic Branczyk wrote:
>
> 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/ac75d9ca-d5c1-4c77-aad2-991bbc9c9889o%40googlegroups.com.


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

2020-06-13 Thread Naseem Ullah
The Prometheus chart clearly has optional installable sub chart for ksm.
We can factor our alertmanager with this chart I've prepared: 
https://github.com/helm/charts/blob/master/stable/prometheus/requirements.yaml
We can also factor our node exporter with either a new node-exporter chart 
or 
https://github.com/helm/charts/tree/master/stable/prometheus-node-exporter

We are ready to get going, I've had success migrating other CNCF charts 
such as https://github.com/jaegertracing/helm-charts and 
https://github.com/fluent/helm-charts/tree/master/charts/fluent-bit

Please allow me to lead this effort by providing an empty helm-charts repo 
under https://github.com/prometheus-community.

On Tuesday, June 9, 2020 at 12:15:27 PM UTC-4, Frederic Branczyk wrote:
>
> 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/cda40f08-08f4-4723-abc0-09a2fe2326d5o%40googlegroups.com.