Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facilitate pushing charts to a registry #3564

Open
jzelinskie opened this Issue Feb 23, 2018 · 3 comments

Comments

Projects
None yet
6 participants
@jzelinskie
Copy link
Contributor

jzelinskie commented Feb 23, 2018

Historically, Helm has treated chart repositories as read-only.
This has immediate benefits in that charts can be hosted directly by any static webserver or object store. The downside to this approach is that it requires manual updating of the index both client-side and server-side in order to synchronize changes. This inability to easily add a new chart has effected the discoverability and sharing of community charts outside of the official charts repository.

In order to combat this problem, there are two existing community solutions: App Registry and ChartMuseum. Both offer a workflow for uploading charts to a remote service that will serve charts.

ChartMuseum strives to match the existing Helm repository model with the addition of HTTP methods for mutating charts. The ChartMuseum server acts a centralized point of generating the Chart repository index after one of the mutating HTTP methods is called. An example of this workflow can be achieved using Helm and cURL.

App Registry eschews existing Helm repository design in favor of a model that aligns with existing registries used for container images. App Registry does not create any Helm repositories or indexes, rather it leverages a docker-style registry protocol for uploading, downloading, and discovering charts. Charts are treated as opaque blobs and stored in content addressable storage (CAS). OCI-style JSON manifests are used to describe the metadata for a collection of blobs. An example of this workflow can be achieved using the Helm App Registry Plugin.

I'm opening this issue as a long-term discussion for how we should potentially move forward with improving Helm core to better support these workflows.

@jascott1 jascott1 added the proposal label Feb 23, 2018

@SlickNik

This comment has been minimized.

Copy link
Member

SlickNik commented Feb 26, 2018

Thanks for kicking off this discussion @jzelinskie! We spoke about this during one of the unconference sessions at the Helm summit (Session 1 - Table 2). I've compiles some notes from that session and have opened a PR at helm/helm-summit-notes#4.

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented May 27, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jun 26, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.