このページの情報は古くなっている可能性があります。 最新の情報は 本家サイト でご確認ください。
Users or organizations that deploy complex pieces of software towards Kubernetes managed environments depend on a standardized way to automate provisioning those external environments. Helm is the package manager for Kubernetes and helps users define, manage, install, upgrade, and rollback even the most complex Kubernetes application. Helm uses a package format called Charts to describe a set of Kubernetes resources. There is a clear path towards utilizing GitLab's Container Registry and new features in Helm 3 to provide a single location for Helm Charts within the Container Registry. GitLab will join the open source community in enabling this capability and improve upon it with features targeted at our EE offering.
Helm charts will be easy to create, version, share and publish right within GitLab. This would provide an official and integrated method to publish, control, and version control Helm charts.
This page is maintained by the Product Manager for Package, Tim Rizzi (E-mail)
With the launch of Helm 3, which is now in beta, pushing and pulling charts can now be done via OCI Registry. This means that users can now utilize the GitLab Container Registry for hosting Helm charts. However, due to the way metadata is passed and stored via Docker, it is not currently possible for us to parse this data and meet our performance standards.
The first step is gitlab-#207147, which defines a new database schema for storing Docker manifests.
This category is currently at the "Minimal" maturity level, and our next maturity target is Viable (see our definitions of maturity levels). Key deliverables to achieve this are:
Helm Hub is the official Helm charts repository, which is supported by products like Artifactory from Jfrog and by Codefresh. Additionally, Chart museum offers an open sourced self-managed solution, aside from being able to code one yourself with GitLab pages, Apache, or by using a GH repo's raw publishing url.
The Azure container registry can be used as a host for Helm chart repositories. With Helm 3 changing the storage backend to container registries, we are evaluating if we can offer the same level of support.
There are currently no customer success or sales issues.
gitlab-#38047 is currently the top customer issue.
There are currently no internal customer issues.
Our current vision is focused on implementing the MVC of the Helm Charts Repository as captured in gitlab-#2281.