Hi everyone
I'm helping with the overall helm stable repo move to find the charts their
new homes (see https://github.com/helm/charts/issues/21103 for overview
status of each chart, and please help us keep those updated by linking to
that issue).
In order to speed this up a bit for
Hi folks. Was a conclusion reached on this? I am a PM at Sumo Logic and we
use the Helm charts as part of our solution and was not sure if a concensus
had been reached.
On Tuesday, June 30, 2020 at 2:27:03 PM UTC-6 husson@gmail.com wrote:
> Up,
>
> @Prometheus Developers for the vote,
Up,
@Prometheus Developers for the
vote, maybe you would like to do it in another topic ?
@Stuart yeah for the option 3 it would make more sense to have in a
dedicated organization. But the idea is there at least :)
Le mar. 23 juin 2020 à 14:42, Stuart Clark a
écrit :
> On 2020-06-23 09:30,
On 2020-06-23 09:30, Augustin Husson wrote:
@Mingchin Hsieh Sorry I didn't get your point. To enable the CI/CD
with circle-ci, yes you need to have the admin right. Otherwise to see
how the CI/CD is working you don't need any special right.
@Cedric that's nice ! I didn't know about it. Thanks a
Hi Augustin,
No problem; just curious if prometheus-community reviewers / owners need
help.
Best,
Mingchin
On Tue, Jun 23, 2020 at 4:30 PM Augustin Husson
wrote:
> @Mingchin Hsieh Sorry I didn't get your point. To
> enable the CI/CD with circle-ci, yes you need to have the admin right.
>
@Mingchin Hsieh Sorry I didn't get your point. To
enable the CI/CD with circle-ci, yes you need to have the admin right.
Otherwise to see how the CI/CD is working you don't need any special right.
@Cedric that's nice ! I didn't know about it. Thanks a lot :)
I think here we need to have a vote,
BTW, for maintainers of prometheus-community, do you guys need to be
granted as one of owners in prometheus-something chart in order to see or
have a taste of the current helm stable chart CICD process?
If so, please let me know, or ping any helm members. Thanks.
On Mon, Jun 22, 2020 at 10:40 PM
Hello,
prometheus-something chart maintainer here. ;)
Actually, it is quite simple to use https://github.com/helm/chart-testing
(and if you're going to use GitHub Actions,
https://github.com/helm/chart-testing-action) and/or
https://github.com/helm/chart-releaser, which automates all the
Hello,
Well having a single repo for each chart would create so much repositories
and IMHO just imagine to create for each of them the CI/CD even if it's the
same each time, is to exausting. ( Yeah I'm a bit lazy)
Moreover if you have to change one CI/CD for whatever reason you will have
to
Hi André,
I would take back what I said. I originally intended to not mess-up repos
under prometheus-community and might think too much on current CI e2e
testing stucking issues.
Best,
Mingchin
On Sat, Jun 20, 2020 at 1:50 AM André Bauer wrote:
> Why would you want to add "helm-chart" in the
Why would you want to add "helm-chart" in the name of the chart and have
multiple repos?
Imho it would be:
helm-charts/prometheus
helm-charts/alertmanager
helm-charts/...
and so on. So being "helm-charts" the repos main directory and the charts
inside of it.
Adding "helm-chart" to the name
Hi Stuart,
No. My ideal expectation would be different repos, unless cost and / or
maintenance is too high.
Best,
Mingchin
On Fri, Jun 19, 2020 at 10:26 PM Stuart Clark
wrote:
> On 2020-06-19 15:09, Mingchin Hsieh wrote:
> > Hi,
> >
> > I sort of agree with Stuart's idea; only a little tweak:
On 2020-06-19 15:09, Mingchin Hsieh wrote:
Hi,
I sort of agree with Stuart's idea; only a little tweak: adding
helm-chart as prefix or suffix. For example,
Prefix approach -
helm-chart-prometheus-adapter
helm-chart-prometheus-blackbox-exporter
Hi,
I sort of agree with Stuart's idea; only a little tweak: adding helm-chart
as prefix or suffix. For example,
Prefix approach -
helm-chart-prometheus-adapter
helm-chart-prometheus-blackbox-exporter
helm-chart-prometheus-cloudwatch-exporter
On 2020-06-19 13:30, André Bauer wrote:
Hey guys,
great to see there is already some effort to move the chart out of the
stable repo :)
As i understand that "prometheus" is not the perfect fit for the chart
name, as it also installs other components from the prometheus eco
system, i'm also not
Hey guys,
great to see there is already some effort to move the chart out of the
stable repo :)
As i understand that "prometheus" is not the perfect fit for the chart
name, as it also installs other components from the prometheus eco system,
i'm also not the biggest fan of umbrella charts.
Yes a single repo called helm-charts to host all charts.
Also, as per https://prometheus.io/docs/introduction/overview/#architecture we
should have a prometheus-server chart that would be part of the umbrella
prometheus chart if we want to follow this pattern.
On Sunday, June 14, 2020 at
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 a écrit :
> Hi Frederic,
>
> Yes. I think I would keep straightforward naming as prometheus-helm-chart,
> i.e.
>
>
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
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
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
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
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
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
+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
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
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,
Ping... Ben, any opinion on how to proceed?
On Thu, Apr 16, 2020 at 2:24 PM Julius Volz wrote:
> +cc SuperQ (Ben)
>
> Sounds reasonable to me at a first glance.
>
> On Wed, Apr 15, 2020 at 2:56 PM Naseem Ullah wrote:
>
>> bump
>>
>> --
>> You received this message because you are subscribed to
+cc SuperQ (Ben)
Sounds reasonable to me at a first glance.
On Wed, Apr 15, 2020 at 2:56 PM Naseem Ullah wrote:
> bump
>
> --
> You received this message because you are subscribed to the Google Groups
> "Prometheus Developers" group.
> To unsubscribe from this group and stop receiving emails
bump
--
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
30 matches
Mail list logo
