Or just helm-chart with inside all chart relative to the prometheus tools
like node-exporter, alertmanager ...etc.

Le dim. 14 juin 2020 à 13:52, Mingchin Hsieh <[email protected]> a écrit :

> Hi Frederic,
>
> Yes. I think I would keep straightforward naming as prometheus-helm-chart,
> i.e.
>
> https://github.com/prometheus-community/prometheus-helm-chart
>
> If you guys have better idea on naming, please advice.
>
> Best,
> Ming
>
> On Tuesday, June 9, 2020 at 6:44:26 PM UTC+8, Frederic Branczyk wrote:
>>
>> 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 <https://github.com/coreos/kube-prometheus>).
>>
>> On Thu, 4 Jun 2020 at 23:50, Mingchin Hsieh <[email protected]> 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
>>>> <https://github.com/helm/charts#deprecation-timeline>, the various
>>>> prometheus related helm charts such as prometheus
>>>> <https://github.com/helm/charts/tree/master/stable/prometheus>,
>>>>  prometheus-operator
>>>> <https://github.com/helm/charts/tree/master/stable/prometheus-operator>
>>>> , prometheus-adapter
>>>> <https://github.com/helm/charts/tree/master/stable/prometheus-adapter>
>>>> , prometheus-node-exporter
>>>> <https://github.com/helm/charts/tree/master/stable/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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/prometheus-developers/53909810-686f-4550-977a-4f1c721dc8fao%40googlegroups.com
>>> <https://groups.google.com/d/msgid/prometheus-developers/53909810-686f-4550-977a-4f1c721dc8fao%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/d4b915e1-e758-4c8f-b747-15a795705e8fo%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/d4b915e1-e758-4c8f-b747-15a795705e8fo%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CAOJizGc9FRUY532fevasWa4PG8T0_0uErZPiF8FqXL04BRk0ew%40mail.gmail.com.

Reply via email to