Helm v3.4.0 and v2.17.0 were both released. Along with that the details on the new location for the stable and incubator chart repositories are available. Details are in the blog post at https://helm.

Today, Oct 19th, is Helm's 5th birthday. Along with that we have an announcement about GitHub and the stable/incubator charts... https://helm.sh/blog/helm-turns-five/

The Helm Hub has now migrated to the Artifact Hub. Details are available in the blog announcement at https://helm.sh/blog/helm-hub-moving-to-artifact-hub/ If there are any questions or comments there

The Helm project has decided to deprecate the Helm Hub and redirect people to the Artifact Hub. We have been tracking this work for some time. We are now at the point where the redirect will go into p

I wanted to share that we have made a small governance change to Helm. There was a section in the governance that pertained to the initial election of org maintainers. That event happened a couple yea

Teja, This is a good question. There are a couple things that come to mind for uses of Helm tests. Helm tests enable a chart author to package tests in a chart and ship them to a chart consumer. The c

This has been shared previously but we've come to realize that not everyone has noticed. On November 13th of this year the stable and incubator chart repos will be marked obsolete and will be going aw

The Helm Hub has made it far easier to find charts that are distributed around the Internet. General purpose search engines don't make it easy and the Helm Hub, being Kubernetes and charts specific, p

Berin, I am not entirely sure of your workflow so these are just ideas and thoughts in the area. First, appVersion is optional. You do not need to use it if you don't want to. Second, if you are using

Berin, Thanks for such an extensive write-up. I can't address all of it now but I wanted to talk about transitive dependencies. I am curious what you are looking for in respect to that as far as handl

Thanks for suggesting the Kubernetes process. I'll take a look at it. I just took Gitlocalize for a spin. I had a couple problems with it (i.e., hugo front matter handling and DCO). Won't work for us.

I'm kinda interested in the human based tools more than automating translations. From what I've been told, the automation quality is so-so. But, we have people interested in translating docs. But, our

The Helm website and docs are setup for localization / i18n. The flow of contributing translations is the same as contributing docs and code. This has left me wondering... should Helm use some outside

s/not/now .... Helm v3.1.0 has NOW been released. Thanks for catching my typo Jimmy.

Helm v3.1.0 has not been released. You can read about it at https://github.com/helm/helm/releases/tag/v3.1.0 There was about 3 months between the release of 3.0.0 and 3.1.0. The release of 3.0.0 was a

Part of the process for Helm to become a graduated CNCF project is to complete an independent and third party security audit with the results being published. As part of the audit of Helm 3 a security

If you are going to work with both Helm v2 and Helm v3 in your scripts this email is where we are looking for your input. `helm version` in v2 and the forthcoming v3 work a little different. This incl

+ Steve

Steve, you ask a great question here. Specifically... At KubeCon/CloudNativeCon EU this year we learned that there is good demand for Helm v3 sooner rather than later. Specifically, a Helm without Til

Hi Joni. Is this flight simulation system one application with numerous microsevices? If so, it may make sense to do it as a single chart. That's what I would do. Are you going to share this chart pub