> Is the Helm team providing any CI assistance to self-hosted repositories?
The testing tools are freely available (
https://github.com/helm/chart-testing) but they don't provide any
infrastructure. We can potentially use something like Kind (
https://kind.sigs.k8s.io/) on Jenkins for deployment testing.

On Thu, 26 Sep 2019 at 17:31, Adam Kocoloski <kocol...@apache.org> wrote:

> It’s certainly a pain to get the Helm maintainers to approve Pull
> Requests, so I’m glad to see a strategy here.
>
> Is the Helm team providing any CI assistance to self-hosted repositories?
>
> Part of me wonders if ASF would want to host a repository to which all
> projects could contribute but I don’t personally feel like spending the
> cycles to find out :) I’m quite ok with CouchDB hosting its own.
>
> Adam
>
> > On Sep 26, 2019, at 12:18 PM, Will Holley <willhol...@gmail.com> wrote:
> >
> > Hi all,
> >
> > CouchDB has a mature Helm chart at
> > https://github.com/helm/charts/tree/master/stable/couchdb to facilitate
> > deploying CouchDB clusters to Kubernetes. Historically, Helm charts have
> > been curated by the Helm team alongside a list of chart-specific
> > maintainers (@kocolosk in this case).
> >
> > The Helm team have indicated that the current monolithic repository
> > approach is unsustainable for them and have started asking chart owners
> to
> > move to self-hosted repositories (most commonly GitHub pages -
> > https://github.com/helm/hub/blob/master/docs/github.md). These are then
> > aggregated at http://hub.helm.sh.
> >
> > What do people think about moving the CouchDB chart from the helm/charts
> > Git repository into an Apache-owned repository (e.g.
> > github.com/apache/couchdb-helm) to complement the existing
> > apache/couchdb-docker repository?
> >
> > If there's appetite for this I can move to a vote.
> >
> > Thanks!
> >
> > Will
> >
> > p.s. for those interested, the workflow for deprecating the existing
> chart
> > is described at
> >
> https://github.com/helm/helm/blob/master/docs/charts.md#deprecating-charts
> .
>
>

Reply via email to