Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Gitlab Official Chart #1138

Closed
kwent opened this issue May 22, 2017 · 4 comments
Closed

Gitlab Official Chart #1138

kwent opened this issue May 22, 2017 · 4 comments

Comments

@kwent
Copy link
Contributor

kwent commented May 22, 2017

Gitlab Official Charts

Gitlab just released their official charts, might be worth is to deprecate or mention it for:

Regards,

@rimusz
Copy link
Contributor

rimusz commented May 23, 2017

maybe to contact Gitlab guys and ask to publish the new charts here?

@twk3
Copy link
Contributor

twk3 commented Jun 9, 2017

Some discussion on this has gone on here: #608 (comment)

and here: https://gitlab.com/charts/charts.gitlab.io/issues/10#note_29333155

Instead of a gitlab-ce and gitlab-ee chart, we have a gitlab chart that can be used for either. Our chart is a renamed iteration of the gitlab-ce chart from this repo.

We want to be able to iterate faster on our charts than the review process here in this repo, but we also value the review feedback we get here.

We do plan to keep our own repo, and continue iterating and officially supporting the charts there. But are open to suggestions on how to deal with the charts in this repo.

@viglesiasce
Copy link
Contributor

We are going to be looking at how to delegate the responsibility of these charts in the near future. If you have ideas on how you'd like to see this work please let us know.

@lambertjosh
Copy link
Contributor

lambertjosh commented Aug 28, 2017

@viglesiasce our general plan would be to deprecate the existing charts here in this repo, and then introduce the officially supported charts, gitlab-omnibus and gitlab-runner. These chart names would also handily avoid name conflicts. We really appreciate all of the work done here on these charts by the community.

If there is some way for a set of authorized GitLab maintainers to more quickly update these here either manually or via CI that would be very helpful. Right now we are actively improving our charts, so we tend to push updates relatively frequently.

Perhaps a bot could auto-approve PR's from a company's maintainers, or instead automatically sync with an upstream repo periodically?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants