We were looking to use Lua as a pre- and post-hook event system when charts were being rendered. The post-render hook introduced in Helm 3.1 seems to handle most of the use cases the Lua event system

Hi guys, I'm interested in the move to supporting Lua templates, is there a technical discussion or documentation discussing the reasoning behind Lua as a language choice? I would like to put forward

Thank you Gareth. At a first glance it looks good and I will surely try it out. -- SIMON FONTANA OSCARSSONSoftware DeveloperEricssonÖlandsgatan 137133 Karlskrona,

As one of the maintainers I'm biased, but try out Conftest https://github.com/instrumenta/conftest We have a Helm plugin which makes this easier

Hi, Are there any good options for writing unit tests for Helm charts? My use case is that I want to test that, when setting a parameter, the correct changes are applied to the chart. I've looked a

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

I created the Helm 2 Weave Scope chart, and I’ve been looking at it in light of the recent GA of Helm 3, and a lot of what I need to do with it is security-related: * It needs version/default

Hi all: Reaching out re: help for a CNCF webinar on Feb. 25th (date and time is final). There is flexibility WRT content. Will include the Helm report (see below) but will be great to have something

This feature is being tracked in https://github.com/helm/helm/issues/5303. It is not currently available. However, the implementation details seem easy enough for someone new to the Helm code base to

Does helm 3 supports impersonation similar to ‘as’ in kubectl?

Thank you very much, Fox and Kevin. That cleared up my confusion.

Sorry, I meant to say "Thanks, Kevin and Matthew"!

> My guess is that, during the 3-way merge, the mentioned "old manifest" is directly retrieved from the k8s master itself and that Helm doesn't store any release related information in the

As far as I can tell, the "state" is made up of: * caches * credentials * repos So long as your stateless job (k8s pod) adds whatever credentials it needs and repo's as part of the job you should be

Hi, I'm sorry if the question comes across as too lame. Now that Helm 3 is client-only, I understand that it stores "state" information along with the client in the directories determined by the

Hi Paul! Thanks for answering. Actually I already tried your second approach with somescripting voodoo around it which of course worked. But meanwhile I came across abetter solution by using the k8s

Hi Bernd! I could see two options: * use the `post-install` hook for the pipeline-run ? * use two helm charts, one for the tasks and pipeline, the other for the pipeline-run. the latter can have

Hello All, I want to use templates in overall umbrella chart and include/build only required helm chart. Which means the Final umbrella chart(main values.yaml) should only contain information about

According to the documentationhere it is possible to declare dependenciesin Heln charts using the charts subdirectory. However, the order in which theK8s resources will be deployed depends on the