I would like to propose a process to "lock" a helm release to a specific version so it is safe from `helm upgrade` and other situations that may cause unintended breaking changes. There are a variety

Hi, Following the HIP process, I'd like to know whether the use-case below already received some thoughts, and whether there are some suggestions on best user experience to support this use-case. I ha

Hi, I was looking for the list of tests that can be executed or recommended to execute on a helm chart. Does anyone have a good handy list that can be seen as a good starting point? One observation, m

Hi all, Following the HIP guide. I am looking for feedback regarding my idea below: The current Helm uninstall implementation is marking release record as uninstalled even if Helm detected errors duri

JFrog https://Chartcenter.io services will be deprecated soon. Please read more about it at https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

You'll have to forgive my ignorance on this one, but there is nothing I can see that explains this design decision--and it really makes creating multi-service deployments harder than it should be. In

The preferred method is requiring the user to set a value that points to an existing secret. If the user points to the wrong thing, then Helm should fail to deploy that release. We advise people not t

Example: I am creating a chart for a single page app server. In it I want the ability to add a reference to the TLS secret. The TLS secret would be provided by the person using the chart. In my chart

Hi, helm 3.5 will be released next week Wednesday, January 13th as previously announced. At the same time we should announce when the 3.6 release is planned. On the dev call today it was suggested: 3.

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.

Good morning/afternoon/evening (delete as applicable) I've been directed to this mailing list by Martin Hickey and Matt Fisher due to a proposal I have briefly mentioned at https://github.com/helm/hel

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

Hi, I want to understand why we need helm tests? I have my CI automation which deploys all of my charts and checks if the feature is working or not. I don't understand why I need "helm tests" in the h

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

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

Hi, I am writing to formalize a proposal to extend Helm 3 in a backward compatible manner to allow passing derived values to subcharts without exposing them in `values.yaml`. I wrote this an issue on

Hey Helmettes, It's been a pleasure being a core maintainer on the Helm project since it's initial release Helm Classic (v1) in 2015 and probably the coolest experience of my career. I am officially s