I see the reason of doing this. I use a similar thing myself, although not as complete. With helm and also plain kube yamls you tend to repeat code across yamls

I see the reason of doing this. I use a similar thing myself, although not as complete. With helm and also plain kube yamls you tend to repeat code across yamls and across projects. On a separate topic, one great thing about helm is it's declarative+state nature, much like terraform. I love using helm because it makes sure you don't leave leftover yaml components in your cluster anytime you make a mistake when you delete projects or rename yaml files in your local directory. One thing that I don't like about kubectl apply, that doesn't get fixed "just by" using helm, is that it will leave changes that someone could have run manually through kubectl imperative commands. I didn't check the repo but if it implements all defaults in the template, that could solve this issue partly